-
-
Notifications
You must be signed in to change notification settings - Fork 848
Closed
Labels
Complexity: LargeFeature: Refactor GHARefactoring GitHub actions to fit latest architectural normsRefactoring GitHub actions to fit latest architectural normsLang: GHAGitHub ActionsGitHub Actionsready for dev leadIssues that tech leads or merge team members need to follow up onIssues that tech leads or merge team members need to follow up onrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 3ptCan be done in 13-18 hoursCan be done in 13-18 hours
Milestone
Description
Overview
Dev leads have noticed that the Add-Missing-Labels-to-Issues job is failing whenever we submit a new issue onto the project board. We need to correct the job so that it works correctly and adds missing labels to issues that are submitted for approval.
Action Items
- See associated issue ER: Add-Missing-Labels-to-Issues job fails when opening an issue #4129 for more information
- Familiarize yourself with GitHub Actions
- Understand the HfLA GitHub Actions by reviewing the wiki and the different GHAs we use
- If you have not already done so, create a copy of the Project Board into your own repo (Tip 6: Creating your own Project Board)
- Be sure to read up on using Personal Access Tokens to test the project board in your own repo (Tip 7: Using Personal Access Tokens to test in your own Project Board)
- See issue-trigger.yml and investigate what the issue may be
- Determine if there are any deprecated functions that may be causing the issue
- For testing purposes, create and edit tokens as necessary for your repo
- Make corrections to workflow and test in your local repo to ensure that it works
- Provide a demo to the merge team for review
Resources/Instructions
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Complexity: LargeFeature: Refactor GHARefactoring GitHub actions to fit latest architectural normsRefactoring GitHub actions to fit latest architectural normsLang: GHAGitHub ActionsGitHub Actionsready for dev leadIssues that tech leads or merge team members need to follow up onIssues that tech leads or merge team members need to follow up onrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 3ptCan be done in 13-18 hoursCan be done in 13-18 hours
Type
Projects
Status
Done