+ We welcome contributions! You can help by adding new features, fixing + bugs, or improving the project. Just make sure to follow our + guidelines to avoid conflicts. +
+
+ {`## Contribution Guidelines
+
+Contributions to devpulse are welcome! Please follow these guidelines:
+
+1. Before modifying any existing design or logic that is already working or in use, **contact us first** to avoid conflicts.
+2. You are welcome to contribute new features, bug fixes, or improvements.
+3. Check the Issues tab (if available) before starting to avoid duplicate work.
+4. Follow the existing code style and conventions.
+5. Submit a pull request with a clear description of your changes and the problem it solves.
+
+> ⚠️ Pull requests that modify existing working features without prior discussion may not be merged.
+
+Help us keep the codebase ("DevPulse") clean, stable, and maintainable.`}
+
+ + Thank you for considering contributing to DevPulse! To + help maintain the quality, stability, and integrity of our codebase + ("Hall of Codes"), please read and follow these guidelines. +
+ ++ Please reach out to us before modifying any existing design or logic + that is currently working or in active use. This ensures we avoid + conflicts and preserve the stability of DevPulse. +
+ +You are welcome to:
++ Before submitting a pull request (PR), check the Issues{" "} + tab if it exists to avoid duplicating work or causing conflicts. +
+ ++ Any PR that modifies existing, working code without prior discussion may + not be merged. We reserve the right to reject contributions that + conflict with ongoing development or compromise the stability of the + DevPulse. +
+ ++ Our codebase represents the core of DevPulse. + Contributors are expected to respect coding standards, write clean, + maintainable code, and document changes clearly. Unauthorized + modifications, destructive changes, or attempts to bypass review + processes are not allowed and may result in removal of the contribution. +
+ ++ By contributing, you agree to follow these guidelines to keep DevPulse + stable, reliable, and enjoyable for all users. +
++ We use Sentry for error monitoring. While only error-related features + are enabled, Sentry may still collect certain information, including + personally identifiable information (PII), stack traces, and request + data. This information is used solely to help diagnose errors and + improve the reliability and performance of the application. +
+We are not responsible for the availability, accuracy, or practices of @@ -66,6 +67,11 @@ export default function Terms() { responsible for keeping your API key secure. We are not liable for any misuse resulting from unauthorized access to your key.
++ When you visit us and an error occurs, we may use Sentry to capture + error details. This helps us improve the service, but we do not use this + data for any other purpose. +
@@ -87,9 +93,9 @@ export default function Terms() { 7. Limitation of Liability
- DevPulse is provided "as is" without warranties of any kind. We are not - liable for any damages, including loss of data, arising from your use of - the service. + DevPulse is provided "as is" without warranties of any kind. + We are not liable for any damages, including loss of data, arising from + your use of the service.