-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added the feedback form(both frontend and backend logic) #260
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊 |
conflicts |
@PatilHarshh I will recheck my code and try to resolve the conflicts |
@PatilHarshh i have resolved the conflicts and incorporated latest changes into my code from the main branch. I have created a new PR resolving these issues, please go through that and merge my PR. Thank you |
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
11775317 | Triggered | Generic High Entropy Secret | 6aaa592 | client/dist/assets/index-1f76e8ca.js | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
@PatilHarshh please review my code, it doesn't contains any merge conflicts, merge this PR |
@PatilHarshh PLEASE MERGE MY PR |
Related Issue
This pull request is related to issue #234
Description
user gives their details and write feedback and also rate our app experiance on a scale of 5.
Type of PR
Screenshots / videos (if applicable)
Checklist:
Additional context:
I request the admin to please review my code and merge this PR. I am open to any suggestions or modifications
Thank you