Varaprasad #1
Open
Varaprasad #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… files" This reverts commit b110970.
1. Replaced old Login with Google Login 2. Added title as "Event Permissions" 3. Added IITDh Logo 4. Resolved some image import warnings (/public directory is served as root)
1. Completed the frontend of Event Form page (by adding all the required variables to store the form data). 2. Formatted the pdf using jsPDF using all the form data variables . 3. Instead of downloading the pdf each time, added iframe to display the pdf on the webpage itself (which will have a download button in the frame itself)
1. Renamed and added the variables required for filling and storing the form in official format. 2. Added the "Submit for Approval" button along with checking "All required fields should be filled"
My Event Applications page to show event form applications previously applied for. (It shows pending applications in "Yellow" and approved applications in "Light Green")
In Staff Dashboard, made these work: 1. Pending Applications 2. Approved Applications
1.View Details Button for Pending Applications Inside DetailsPage 1. Approve button working 2. Reject Button working
Separated generatePDF() function from EventForm.jsx and EventDetails.jsx into src/utils/pdfGenerator.js
& Event Details header size fixed.
Utkarsh-Updated master branch to latest version
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 15701368 | Triggered | MongoDB Credentials | b110970 | backend/.env | View secret |
| - | - | MongoDB Credentials | b110970 | backend/.env | 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 secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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.
Varaparasad
force-pushed
the
Varaprasad
branch
from
80d8f41 to
dc18409
Compare
Varaparasad
force-pushed
the
Varaprasad
branch
from
94ea528 to
dc18409
Compare
Updating branch "Utkarsh" with the "main" branch.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.