Syncing .buildconfig/ci-linux.yml with requirements/*.txt
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 4
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 5
Description
Currently the doc build env (specified by .buildconfig/ci-linux.yml) needs to be maintained independent of the pinned env generated by tox -e deps. This can lead to inconsistencies and we should figure out a way to keep these things in check.
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
Compare .buildconfig/ci-linux.yml with the pinned files under requirements/ and inspect the tox -e deps environment generation. Determine how the doc build environment and generated requirements can be kept consistent, then verify that the chosen approach prevents future divergence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100