Skip to content
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 GHAs so templates use label-directory.json #7688

Conversation

t-will-gillis
Copy link
Member

@t-will-gillis t-will-gillis commented Nov 4, 2024

Fixes #7687

What changes did you make?

  • Refactored check-labels.js so that templates labeled with Template Label Placeholder will trigger a function to find labelKeys in the body comments and then convert these to labelNames.
  • Refactored blank-issue-template.md and inactive-members.md as example cases of how this will work. The remaining templates will be changed in a later issue.

Why did you make the changes (we will use this info to test)?

  • Providing the supporting functionality so that templates will use labelKeys and reference the label-directory.json

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

Screenshot 2024-10-28 154514

Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.

  • I have checked this PR for CodeQL alerts and none were found.
  • I found CodeQL alert(s), and (select one):
    • I have resolved the CodeQL alert(s) as noted
    • I believe the CodeQL alert(s) is a false positive (Merge Team will evaluate)
    • I have followed the Instructions below, but I am still stuck (Merge Team will evaluate)
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
  • Test logs and screenshots to follow

Copy link

github-actions bot commented Nov 4, 2024

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.

git checkout -b t-will-gillis-refactor-gha-templates-labels-7687 gh-pages
git pull https://github.com/t-will-gillis/website.git refactor-gha-templates-labels-7687

@github-actions github-actions bot added role: back end/devOps Tasks for back-end developers Complexity: Large Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms size: 5pt Can be done in 19-30 hours labels Nov 4, 2024
@t-will-gillis t-will-gillis marked this pull request as draft November 4, 2024 22:17
address CodeQL concern for undeclared variable
added explicit semicolon to address CodeQL alert
@t-will-gillis
Copy link
Member Author

The specific task to use label key values on the template files will be addressed in a future issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms role: back end/devOps Tasks for back-end developers size: 5pt Can be done in 19-30 hours
Projects
Development

Successfully merging this pull request may close these issues.

Refactor GHAs so that Templates use label-directory.json
1 participant