-
-
Notifications
You must be signed in to change notification settings - Fork 843
Updated CoP DevOps Name #8455
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
base: gh-pages
Are you sure you want to change the base?
Updated CoP DevOps Name #8455
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: 1/9/26 |
lc1715
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.
Great job @cadenramey!
The PR contains the linked issue and has the correct branch to commit into and from. I can see the name change from 'Ops' to 'DevOps' and the meeting times show up in the browser as well. Thank you!
myronchen-git
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.
Good job on the troubleshooting.
I've tested the Communities of Practice webpage, and it works as expected. I've also did a quick check to see if anything else uses ops.yml file to see if the name change affected any other code, but I didn't find anything, although I may be wrong.
Thanks for getting this done.
Fixes #8388
What changes did you make?
ops.ymlfrom Ops to DevOpscommunities-of-practice.jsWhy did you make the changes (we will use this info to test)?
ops.ymlin order to more accurately name project informationcommunities-of-practice.jsin order for the corresponding html file to be mapped to the new nameCodeQL 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