-
-
Notifications
You must be signed in to change notification settings - Fork 843
Update Civic Tech Jobs project profile webpage #8304
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 Civic Tech Jobs project profile webpage #8304
Conversation
Removed Kanika Chotani and Jimmy Juarez from the Civic Tech Jobs webpage's leadership. This is done to keep the page up-to-date, because either those two are no longer in leadership or no longer active in Hack for LA.
|
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: 8/31/25 |
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.
Thank you for working on this issue @myronchen-git !
Things Done Well
- Code passes all Code QL alerts
- PR description accurately describes changes and why they were made
- Only the requested file in the issue was changed
- Changes appear on the website and line up with what was asked in the instructions
Requested Changes
None
I approve this PR.
Edit: There is also a CodeQL error for "Memory Activity Trigger" that popped up after I reviewed the PR, I'm not sure if it was because of your code though. I messaged Will to ask for more information.
Thanks for messaging someone about it. I don't know what that is about. Looking into the raw log gives an error of I think I read about a similar problem like that happening to someone else, but I do not remember where that was. |
t-will-gillis
left a comment
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.
Hi @myronchen-git @caz002 @FatCatLikesBeer
As a confirmation- the "Member Activity Trigger" error can be ignored for this PR review.
FatCatLikesBeer
left a comment
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.
@myronchen-git thank you for taking on this PR!
Things Done Well
- Pull request is done in the correct branch
- Issue is properly linked and understandable
- Issue appears to be don with the correct branch
- Appropriate changes reflected in
Files changedtab - Relevant screen shots are correctly placed
- Website still works as expected
- Expected changes are reflected in the website 👍🏽
Requested Changes
- None
Notes
- @t-will-gillis mentioned the failing check can be ignored.
I approve this PR!
Fixes #8084
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