OpenAstronomy / OpenAstronomy/github-actions-workflows
FR: support uploading nightly artifact from a previous run
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 21
- Forks
- 27
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 1
Description
Inspired by https://github.com/matplotlib/matplotlib/blob/main/.github/workflows/nightlies.yml
I would like to propose and explore supporting a workflow where builds are separated from uploading. This would save CPU time by re-using previous build results.
The security implications seem acceptable and possibly non-existent to me; the currently supported workflow (re-build then upload) not being any more secure than this proposal, as far as I can tell.
Is there any appetite for it ?
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 matplotlib's .github/workflows/nightlies.yml with the current build-and-upload workflow in this repository. Trace how builds and uploads are separated, assess the stated security implications, and define what artifact handoff and validation would be required. Done means the workflow design and its implementation or review path are clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100