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
[x] Create new issue
[x] Ensure no special labels
[x] No hard labels: Feature: Refactor CSS, Feature: Refactor HTML, Feature: Refactor JS / Liquid, Feature: Refactor GHA
[x] No soft labels: role: back end/devOps, Feature: Analytics
[x] No override soft label: role: front end
[x] Place issue in the Prioritized Backlog column of the copied HackForLA project board
[x] Assign self and move issue to the In Progress column of the copied HackForLA project board
[x] Close issue
[x] Check if automation runs correctly
[x] 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