Integrate Build Stages for Publishing
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 24
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Currently publishing requires tests to pass two times. We should aim to use build stages to reduce this down to one test passage.
The process would move publishing to the second build stage, only to be executed when the builds have passed, allowing to only publish a binary if everything went right.
- [ ] split project into multiple build phases
- [ ] move publishing to the last phase, only to be executed if the rest works out
We could think about doing an initial step that checks for formatting and so on.
Contributor guide
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
No files, tests, or build entry points are named. Start by locating the project’s build and publishing configuration, then trace how tests and binary publishing are currently ordered. Done means publishing runs in a later stage only after the earlier build and test stages pass, with formatting checks considered if supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100