Improve CI/CD surrounding ACME Client Implementations json

Open
#2,235 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Domain
ci-cd

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.

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.

Dominant language
HTML
Stars
909
Forks
591
Avg merge
10h 40m
Merged PRs (30d)
31

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from letsencrypt/website

All issues in letsencrypt/website

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.