Optimizing Weekly Label Check GHA #1555
Labels
DevOps
type of development task related to Process, Github Actions, and Deployment
feature: GitHub/Project Board maintenance
feature: team operations
issues relating to team processes and operations
issue level I: request
Smallest type of issue; Typically can be completed by one person
priority: medium
role: development
anything related to code
size: 1pt
can be done in 6 hours or less
Status: Update Requested
Milestone
Overview
While fixing a bug related to the Weekly Label Check, some opportunities for improvement have been identified.
When the action fails, it just prints the error in the console and continues on and will 'pass' when it's finished. Rather than have it continue, the action should fail.
The action doesn't currently inform anyone debugging how many issues have successfully been labeled after the action runs. Let's add a counter that prints how many issues were updated at the end of the script.
Lines 91-93 are incorrect. Currently it shows the 'successful' text regardless of if the POST action to OctoKit was successful, and instead based on if there were any labels to be added to an issue. Update this logic to be dependent on the successful POST request to OctoKit.
Action Items
Resources/Notes
Testing GHAs Locally
Weekly Label Check file
The text was updated successfully, but these errors were encountered: