Change label to Status: Unassigned by Bot for previously prioritized issues
#7933
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change label `Ready for Prioritization` --> `Status: Unassigned by Bot`
Change label `Ready for Prioritization` --> `Status: Unassigned by Bot`
Remove "NEW-" prepend from the "statusUnassignedByBot" key
|
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. |
github-actions
bot
added
role: back end/devOps
Edited the console.log() comment for clarity
coding-yost
approved these changes
Feb 24, 2025
Member
coding-yost
left a comment
coding-yost
left a comment
There was a problem hiding this comment.
- All changes look correct and as requested
- pr links to issue
- great title and responses
You're good to go from me, this all looks amazing. Thank you for the hard work.
31 tasks
gmgonzal
reviewed
Feb 24, 2025
gmgonzal
reviewed
Feb 24, 2025
github-actions/trigger-issue/add-preliminary-comment/preliminary-update-comment.js
Show resolved
Hide resolved
gmgonzal
approved these changes
Feb 24, 2025
Member
gmgonzal
left a comment
gmgonzal
left a comment
There was a problem hiding this comment.
Hi @t-will-gillis, thank you for working on this issue. Your changes look good.
Things You Did Well:
- Step 0: PR is done with the correct branch.
- Issue title looks good.
- PR description looks good.
- Step 1: PR links to the correct issue #7881.
- Step 2: Changes appear to address the issue action items.
- Step 3: No visual changes made to the website.
- Step 4: Source code changes look good.
- Step 5: No other issues seen.
PR is approved, well done :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #7881
What changes did you make?
check-complexity-eligiblity.jsandpreliminary-update-comments.js, changed label fromReady for PrioritizationtoStatus: Unassigned by Botlabel-directory.json, edited key by removing "NEW-" prepend from "statusUnassignedByBot"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)