As a Pulp user, I want to validate that my setup is working
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @melcorr (mcorr)
Redmine Issue: 9150, https://pulp.plan.io/issues/9150
This has been reported in the Pulp Community Survey as a concern that some "Checks" documentation would help alleviate.
"how do I validate my setup is working." ... I've written my own checkout test cases to address this because it wasn't obvious how to reuse the Pulp CI checks.
Can we provide documentation as to how a user could reuse the Pulp CI checks?
Alternatively, can we provide some guidance around how users can know when all is good?
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 or tests are named. Start by reviewing the Pulp CI checks and the existing setup guidance, then determine how users could reuse those checks or otherwise verify that a Pulp setup is working. Done means the documentation gives users a clear validation path.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100