Rework actions in `.github/workflows/` to be structured like `setup-env`
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 1
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 1
Description
e.g. .github/workflows/deploy.yaml --> deploy/action.yaml
setup-env can be used as a step to a job, but currently deploy has to be the entire job (not just a step). This means that if we need to add any custom behavior to the deploy flow, we can’t use the one from the Actions repo at all; we have to copy-paste it into the repo locally and alter it from there (example).
Restructuring these actions will allow us to use them in steps while allowing the flexibility to make project-specific adjustments.
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 by comparing .github/workflows/deploy.yaml with the existing setup-env action and review the linked Princeton Manifold example. Rework the workflow actions so deploy can be used as a job step while still allowing project-specific behavior without copying the action locally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100