-
-
Notifications
You must be signed in to change notification settings - Fork 777
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
Added in Closing Span Tag on the About Us Page - Workforce Development Section #6292
Added in Closing Span Tag on the About Us Page - Workforce Development Section #6292
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.
Note that CONTRIBUTING.md cannot previewed locally; rather it should be previewed at this URL:
|
I can take a look at this, should be able to review before the end of this week (Fri Feb 16). Thank you! |
Availability: Weekdays from 9am to 8pm CST |
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.
Great job @evan-ishibashi!
- Your branch looks great
- You correctly linked the issue
- The span tag has been added correctly
The only advice I have is that the docs indicate to note that no changes to the website have been made under "Screenshots of Proposed Changes Of The Website (if any, please do not screen shot code changes)" in lieu of images.
Could you add a a comment like "No visible changes made to website" under the screenshots section?
Thanks for your work on this! :)
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 @evan-ishibashi, the pull request is complete with the correct branch, and the issue is properly linked. Your summary of changes is clear, and I've verified that the code change didn't visually alter the page. Nice work executing the code edit cleanly.
In addition to adding the comment requested by @gaylem, could you please remove the extra bullet points that aren't used in your summary of changes section?
After making these adjustments, re-request a review by clicking on the re-request review circular arrow icon next to the reviewer's name. The PR is ready for approval and merging once those minor edits are completed. Thanks!
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.
@evan-ishibashi thanks for making the updates. PR is approved.
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.
@evan-ishibashi thanks for taking up the issue, @gaylem and @jphamtv thanks for suggesting the changes.
The branches look good, linked issue is correct, changes done correctly in order to resolve linter error, docker-testing was successful too.
PR approved....
@gaylem re-review the issue again, and then it can proceed to further merging stage!! |
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.
Excellent work, @evan-ishibashi! Thanks for making the changes. Approved! :)
Fixes #5365
What changes did you make?
Why did you make the changes (we will use this info to test)?
Screenshots of Proposed Changes Of The Website (if any, please do not screen shot code changes)