letsencrypt / letsencrypt/website
Improve CI/CD surrounding ACME Client Implementations json
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 909
- Forks
- 591
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 31
Description
I recently submitted PR #2234 in relation to removing two entries from data/clients.json whose authors have archived their respective repos.
But this got me thinking that there is clearly scope here to avoid this problem in the future, your CI/CD could/should check clients.json for archived repos. It should not be really left to humans to clean it up.
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 data/clients.json and inspect the repository's existing CI/CD configuration, using PR #2234 for context on the archived-client cleanup. Define a check that detects archived client repositories and verify that CI reports the condition clearly; done means stale entries cannot pass unnoticed.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100