The-Strategy-Unit / The-Strategy-Unit/nhp_inputs
Automate repeated tasks during selection-app release?
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 2
- Forks
- 1
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 6
Description
When we release the selection app, we have to add a new upgrade method and add to the set of available versions. We could try to make this step more automated. It's also not necessarily a big deal for now.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the release procedure checklist at .github/ISSUE_TEMPLATE/release-procedure-checklist.md, particularly the Inputs: Selection app section. Trace where the new upgrade method and available-version set are maintained, then define an automation approach that removes those repeated release steps. Done means the selection-app release process no longer requires those manual updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100