-
-
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
Refactor GHA 'sort-closed-issues.js' #7729
Refactor GHA 'sort-closed-issues.js' #7729
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.
|
Availability: Weekday mornings |
Available: weekdays |
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 @aadilahmed, great work on this issue. The changes you made to sort-closed-issues.js
successfully retrieve the label names from the directory rather than using the hard-coded names, and the functionality is not affected. I tested closing the following issues:
- An issue with a label in
hardLabels
was moved toDone
- An issue with a label in
softLabels
was moved toDone
- An issue with a label in
overrideSoftLabels
was moved toQA
- An issue with none of the listed labels was moved to
QA
In all cases, the GH Action performed as expected. In addition, your PR explains the changes you made and why, and links to the original issue. Well done!
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 @aadilahmed great job on this!
- The code is clean and concise.
- The issue is linked and the sort-closed is refactored very well.
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 @aadilahmed Great job! I have tested this and everything appears to be sorting correctly. Looks great
Thanks for taking on this issue!
Fixes #7530
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)
No visual changes to website.
Tested workflows:
move-closed-issues.yaml