-
-
Notifications
You must be signed in to change notification settings - Fork 782
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
Update Project Profile: Civic Tech Jobs Add Roja Pinnamraju #7832
base: gh-pages
Are you sure you want to change the base?
Update Project Profile: Civic Tech Jobs Add Roja Pinnamraju #7832
Conversation
Want to review this pull request? Take a look at this documentation for a step by step guide! From your project repository, check out a new branch and test the changes.
|
Review ETA: 16 Jan 2025 @ 8 PM (GMT) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @oiseeurmt, thanks for working on this!
Kudos
- The pull request is made with the correct branch.
- The pull request post contains a linked issue, CodeQL alerts have been checked, and the screenshots section is complete.
- The changes to the
_projects/civic-tech-jobs.md
file are accurate. - I can see the changes in my local environment.
- You have claimed the issue well.
Suggested changes
Please make the following changes to the PR post:
- Provide more detail as to why you have made these changes. You can use the "Overview" section of the originating issue for this.
- Remove unused bullet points.
- You could rename the title to "Update Project Profile: Civic Tech Jobs Add Roja Pinnamraju".
For next time:
- Please use a more descriptive branch name for your relevant task such as
civic-tech-jobs-add-Roja-Pinnamraju-7742
. - Try to include date and time when providing progress update or availability and ETA (like shown below).
ETA: 6 PM 3/4/22
Availability: 5-8 PM Monday
After making these changes, re-request a review from me. Feel free to reach out if you need help with anything.
Thanks for the feedback! I made the changes and will note your suggestions and re-requested the PR |
Review ETA: 19 Jan 2025 @ 6 PM (GMT) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one @oiseeurmt, thanks for making the changes. I have approved this PR now. 👍
Review ETA: 5 PM 1/20/25 |
This looks great! I tested it on Windows computer on both Chrome and Firefox browsers. I clicked on the links and made sure they were being redirected to the correct user. The description, explanation of the case, and the code are all great too. Great job, approving this on my end. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved see comment above.
Fixes #7742
What changes did you make?
Why did you make the changes (we will use this info to test)?
CodeQL Alerts
After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.
Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown
Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.
Instructions for resolving CodeQL alerts
If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.
In general, CodeQL alerts should be resolved prior to PR reviews and merging
Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)
Visuals before changes are applied
Visuals after changes are applied