-
-
Notifications
You must be signed in to change notification settings - Fork 844
Removed Emily Eldar's leadership variable #7936
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
Removed Emily Eldar's leadership variable #7936
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. |
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.
Title needs to be more specific, and reason for change needs to be more specific. Please check the CodeQL options.
Requested change: Before and After Images links are broken.
- pr links to issue correctly
- changes are clean and useful
All other changes are great, Thank you for your hard work.
coding-yost
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.
Please review requirements, working before and after images need to be uploaded before approval.
All other changes look great and the issue will be approved once proper documentation of before and after images have been properly uploaded.
|
@rogerioduenas , please comment with your |
|
Review ETA: EOD 2/26/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.
Hi @Christopher-Chhim , thank you for taking on this issue.
Things you did well:
- PR is done with the correct branch.
- PR contains correctly formatted linked issue.
- PR follows correct format.
- The changes are applicable to the issue.
- Website is still user-friendly and links and components still work as intended.
- Source code changes are applicable and clean.
Suggested changes:
- Under “what changes did you make,” please be more specific on which markdown file did you remove the project profile from:
_projects/home-unite-us.md. - Under “why did you make the changes,” please make your reason relevant to the issue and something like
To keep list of active HfLA project profiles up-to-date. - CodeQL Alerts have not been properly checked. Please check if PR had any CodeQL alerts. Then, please check the correct checkbox on this PR under “CodeQL Alerts”.
- Before and after screenshots are not appropriately included and do not properly load. Please drag and drop the screenshot images and wait for them to finish uploading.
Notes:
- In the future, please make your issue branch name more detailed and relate it to the issue. Please follow the correct scheme/format. For example, the issue Update ‘Give’ image credit link and information - #2093 should have this branch name:
update-give-link-2093. No need to change the issue branch name for this issue.
After making these changes, re-request a review from me. Thank you for your hard work!
|
Availability: Monday - Friday, 10:00 AM to 4:00 PM JST |
I can't access my local repository's live server so I can't provide a picture for after the changes have been applied but I believe it will work. |
|
Hello @Christopher-Chhim :) I saw here and it seems that you corrected everything that was necessary for your PR to be approved, but putting the photo after the task was done is important, even if it is possible to run your branch locally on the reviewer's machine, it is important that you can complete all the steps for your PR to be approved. |
|
Hi @Christopher-Chhim! If you need help with running your local environment, I'm happy to help. Feel free to reach out to me on Slack. |
|
@Christopher-Chhim , please update the screenshot after you made the change. |
|
ETA: EOD 3/16 |
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.
Hello @Christopher-Chhim
Thank you for taking this issue. You're contribution is greatly appreciated.
Things That Done Well
- Your PR contains the correct branch.
- You successfully linked your issue.
- The PR title is informative, as are both the what and why for its changes in the contents.
- The website is still functional after changes were made.
- The Source Code changes you committed look awesome and the message clear and concise.
- The before changes visuals are presented clearly.
Requested Changes
- In the
Before and After Screenshotsection, theVisuals After Changes are Appliedimage link is broken. - State your Availability to the Original PR you assign yourself to in the comment section.
Once you make those corrections, re-request me, and I will approve this PR. Great job.
|
Hi @Christopher-Chhim Please leave us a note about when you plan to resolve this PR, and/or whether you need any help with finalizing it. |
xnealcarson
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.
Things Done Well
- The issue has the correct 'commit into': "hackforla:gh-pages".
- The commit from and collaborator names match.
- The linked issue is present.
- The changes made are applicable and clean.
Suggested Changes
- 'Visuals after changes are applied' image link is broken. Please fix.
|
I'm free all day on Friday |
|
I attached the screenshot after I implemented the changes. |
|
Hey @Christopher-Chhim, the images are rendering properly, but there is duplicate markdown syntax. Please delete the duplicates before the correctly formatted image tags: from Visual before section |
I made the necessary changes but unable to re-request a review |
katiejnete
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.
Thank you for your hard work @Christopher-Chhim , I approve this PR.
xnealcarson
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.
Changes look great. Awesome job on this PR @Christopher-Chhim !
dvernon5
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.
Everything looks great. Great job taking all of the feedback and making the correct changes!
The changes requested have been made.
Fixes #7484
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