Modifying GitHub actions for label change from size to level

[SAUMILDHANKAR]

Dependency

• Audit for changing labels from size to complexity #2777

Overview

As a developer, I would like to track the size of an issue in terms of number of hours. In order to achieve that, we need to modify GitHub action automations or other files before changing size labels to level.

Details

We are planning to edit the following labels:

• Size: Good second issue to level: Good second issue
• Size: Small to level: Small
• Size: Medium to level: Medium
• Size: Large to level: Large

However, before doing that we need to edit all the automations that might be dependent on these existing labels, so that no workflows are affected by this change. Refer to issue #2777 for details on which automations might be impacted.

Action Items

• Use the search string in the resources below to confirm that the list of files that use the size labels identified, is complete.
• Refer to Resources section for which files will be impacted
• Test the changes in your own repo and make sure other functionalities are not impacted
• Create a pull request if all looks good in your own repo
  • Note: Discuss a timeline with the merge team and leads to change the actual labels in our repo as this might be needed for the GitHub action to work properly.
• For merge team: Once the pull request associated with this issue is approved and merged, please update and edit Edit label info for the HFLA wiki and contributing.md file #3110 by
  • Checking off the dependency for this issue in issue Edit label info for the HFLA wiki and contributing.md file #3110
  • Editing any action items if required
  • If all dependencies are checked off, please move issue Edit label info for the HFLA wiki and contributing.md file #3110 to the New Issue Approval column, remove the Dependency label and add ready for milestone label.

Resources/Instructions

• GHA architecture spreadsheet
• Events that trigger workflows
• Workflow syntax for GitHub Actions
• https://github.com/hackforla/website/wiki/Hack-for-LA's-GitHub-Actions
• https://github.com/hackforla/website/wiki/HfLA-GitHub-Actions
• https://github.com/hackforla/website/wiki/GHA:-issue-trigger

Code that Reference Size Labels

• Search GitHub Actions Workflow directory for files that contain the string size:
• GitHub actions folder
• GitHub Actions Workflow Directory

1. post-labels-comment.js --> contains many actions that utilize labels using the 'size' attribute one time in the declaration
2. check-labels.js ---> also contains processes that utilize labels using the 'size' attribute one time in the declaration

I will also note that the following phrases were not used throughout the 2 directories listed above. Just the use of "Size:" and labels.

• Size: Good second issue
• Size: Small
• Size: Medium
• Size: Large

Wiki pages that reference size labels

• Search the wiki for "size: medium"

1. https://github.com/hackforla/website/wiki/How-to-read-and-interpret-labels
2. https://github.com/hackforla/website/wiki/How-to-Review-Pull-Requests
3. https://github.com/hackforla/website/wiki/How-to-create-issues

[github-actions]

Hi @SAUMILDHANKAR.

Good job adding the required labels for this issue. The merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels