ci: test `misc/keygen`
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.6k
- Forks
- 1.3k
- Avg merge
- 8h 47m
- Merged PRs (30d)
- 19
Description
Description
Given that keygen is set to publish = false it is excluded from most CI steps.
Motivation
keygen is a useful tool worth testing in our CI.
Are you planning to do it yourself in a pull request?
No
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
Start with misc/keygen/Cargo.toml at line 10 and .github/workflows/ci.yml at lines 309-321; inspect how non-published packages are selected by the CI workflow. Update the relevant CI coverage so misc/keygen is tested, then verify the affected workflow or equivalent local check includes keygen successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100