You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Certain closed issues should be sorted into the Done column in the new Project Board Beta. However, with the new workflow, all closed issues are sorted to the QA column by default.
This issue is testing whether the current code in the .yaml file correctly refactors the GHA to move closed issues with no special (hard, soft, or soft override) label into the QA column.
Action Items
Create new issue
Ensure no special labels
No hard labels: Feature: Refactor CSS, Feature: Refactor HTML, Feature: Refactor JS / Liquid, Feature: Refactor GHA
No soft labels: role: back end/devOps, Feature: Analytics
No override soft label: role: front end
Place issue in the Prioritized Backlog column of the copied HackForLA project board
Assign self and move issue to the In Progress column of the copied HackForLA project board
Close issue
Check if automation runs correctly
If so, copy link to workflow from Actions tab to include in PR
Overview
Testing workflow automation.
Certain closed issues should be sorted into the
Done
column in the new Project Board Beta. However, with the new workflow, all closed issues are sorted to theQA
column by default.This issue is testing whether the current code in the .yaml file correctly refactors the GHA to move closed issues with no special (hard, soft, or soft override) label into the
QA
column.Action Items
Feature: Refactor CSS
,Feature: Refactor HTML
,Feature: Refactor JS / Liquid
,Feature: Refactor GHA
role: back end/devOps
,Feature: Analytics
role: front end
Prioritized Backlog
column of the copied HackForLA project boardIn Progress
column of the copied HackForLA project boardActions
tab to include in PRResources/Instructions
HackForLA Issue
The text was updated successfully, but these errors were encountered: