-
-
Notifications
You must be signed in to change notification settings - Fork 872
Update the GHA helper-script create-new-issue.js #8794
Copy link
Copy link
Open
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issueFeature: InfrastructureFor changes on site technical architectureFor changes on site technical architectureReady for Prioritizationrole: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hoursCan be done in 0.5 to 1.5 hours
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issueFeature: InfrastructureFor changes on site technical architectureFor changes on site technical architectureReady for Prioritizationrole: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hoursCan be done in 0.5 to 1.5 hours
Type
Projects
- StatusShow more project fieldsReady for Prioritization
Overview
We need to update the GHA helper-script create-new-issue.js to eliminate future technical debt.
Prerequisites
Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.
Overview
We need to update the GHA helper-script
create-new-issue.js1 to import the current Agenda Issue number fromstatic-issue-nums.jsonto eliminate future technical debt.Details
We should update the GHA helper-script
create-new-issue.jsto import the current Agenda Issue number fromstatic-issue-nums.jsonrather than using a local hard-coded constant, so that onlystatic-issue-nums.jsonneeds to be updated when the Agenda Issue number changes.If we do not, each year when the Agenda Issue number is updated, the Agenda Issue number will need to be updated in multiple locations.
Action Items
static-issue-nums.jsonincreate-new-issue.js1 with the following :postComment()call currently usingAGENDA_ISSUE_NUMto instead useSTATIC_ISSUE_NUMS.AGENDAResources
Footnotes
create-new-issue.js ↩ ↩2