-
-
Notifications
You must be signed in to change notification settings - Fork 785
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
Add profile for Priyanka Jujjavarapu to the website #7834
Add profile for Priyanka Jujjavarapu to the website #7834
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: 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.
Hey @lc1715, thanks for working on this!
Kudos
- The pull request is made with the correct branch.
- The pull request post contains a linked issue, what changes you made and why are clear, and the screenshots section is complete.
- The changes to the
_projects/website.md
file are accurate. - I can see the changes in my local environment.
- You have claimed the issue well and provided availability and ETA.
Suggested changes
Please make the following change(s) to the PR post:
- For the "CodeQL Alerts" section, please check off the relevant checkbox(es).
After you have done this, re-request a review from me. Feel free to reach out if you need help with anything.
Thank you @mugdhchauhan for reviewing my first pull request! I looked for the CodeQL alerts for this PR and none were found. Please let me know if there is anything else I need to do! |
Review ETA: 21 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.
Hey @lc1715, you did great for your first pull request! Thank you for making the changes. I have approved this PR now. 👍
You could also check off the checkbox in the previous review above. 🙂
Done! :) |
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.
@lc1715 Great job on your Good First Issue
! Your code passed the ABC's, including:
- PR is made from the correct branch
- PR links to the correct issue:
- The correct file
_projects/website.md
was edited - No extra edits were made
- Appearance of the website looks good (Chrome and Firefox)
- Thanks for being so responsive when the first reviewer requested changes as well, that helps a lot
Approved! 👍
@DrAcula27 Thank you for reviewing the pull request! |
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.
I verified the changes are correct and appear the right way on the page, will now merge! Thanks for working on this :)
Fixes #7751
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