Refactor to allow consistent inspect and testing of the build produced in earlier stages
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 139
- Forks
- 52
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
In an ideal world we would be inspecting/testing/publishing the same artifact throughout the pipeline, rather than rebuilding at different stages.
Solutions might include:
- re-merging build and inspect actions
- renaming inspect as build_and_inspect and use only that for CI/CD
- Allow us to specify a prior build to inspect via the CLI
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 reviewing the pipeline's build, inspect, testing, and publishing actions, along with the CLI entry points involved. Determine which approach best ensures that one earlier build artifact is inspected, tested, and published consistently; done means the chosen workflow no longer rebuilds separate artifacts across stages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100