-
-
Notifications
You must be signed in to change notification settings - Fork 847
Open
Labels
BugSomething isn't workingSomething isn't workingComplexity: MediumFeature: Refactor GHARefactoring GitHub actions to fit latest architectural normsRefactoring GitHub actions to fit latest architectural normsReady for Prioritizationrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 3ptCan be done in 13-18 hoursCan be done in 13-18 hourstime sensitiveNeeds to be worked on by a particular timeframeNeeds to be worked on by a particular timeframe
Description
Overview
We need to add an exception to the "Check Closed Issue For Linked PR" workflow so that the bot does not reopen Skills Issues from inactive members that the "Schedule Monthly" workflow attempts to close.
Action Items
Open check-issue-labels-and-linked-prs.js
- Add the label
Complexity: Preworkto the following section. Note that the labelKey 'complexity0' pairs with the labelName "Complexity: Prework":// Use labelKeys to retrieve current labelNames from directory const [ nonPrContribution ] = [ 'NEW-nonPrContribution' ].map(retrieveLabelDirectory); - Add the labelKeys 'er' and 'epic' for the labelNames "ER" and "epic" in the same section.
- Then add the labelKey variables in the following section. (You may want to refactor to more cleanly account for the excluded labels)
// Check if the issue has the labels that will avoid re-opening it. if ( labels.some( (label) => label === nonPrContribution || label.toLowerCase().includes('ignore') ) ) { console.info(consoleMessageAllowClose); return true; } - Optional: If you want to make this into a
Complexity: Largeissue, create an environment to test GitHub Actions by implementing "Resources/Instructions" below. Ask one of the Merge Team to change the complexity for you. - Otherwise make the necessary changes to the JS, then Slack team members requesting confirmation.
Resources/Instructions
- GitHub GraphQL Explorer
- GitHub GraphQL API
- Refer to The "Hack for LA's GitHub Actions" Wiki guide needs additional explanation #6537 (comment), especially Tips 6, 7, and 8, if you have not already created you personal environment for testing.
- How to Test GitHub Actions
- Additional Notes for GitHub Actions
- Initiated by ER ER: Fix bug where Skills Issue reopened after bot closes #8545
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
BugSomething isn't workingSomething isn't workingComplexity: MediumFeature: Refactor GHARefactoring GitHub actions to fit latest architectural normsRefactoring GitHub actions to fit latest architectural normsReady for Prioritizationrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 3ptCan be done in 13-18 hoursCan be done in 13-18 hourstime sensitiveNeeds to be worked on by a particular timeframeNeeds to be worked on by a particular timeframe
Type
Projects
Status
New Issue Approval