w3c / w3c/github-notify-ml-config
Archived repos cause notifications to fail?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 17
- Forks
- 38
- PR merge metrics
- No merged PRs in 30d
Description
One of the repositories we had listed in the public-credentials@w3.org in mls.json was archived (via Github) and the reporting to the mailing list stopped being delivered shortly thereafter. I'm not 100% sure that is the issue, but thought I'd raise this to see if archival of a repository could cause an error. I've since removed that repository in PR #252 and will be able to report back if it works correctly after next Monday. Just mentioning it here in case anyone else hits the same issue.
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the repository entries in mls.json and PR #252, which removed the archived repository. Check whether mailing-list reporting resumes after that removal, as planned, and use that result to determine whether archived repositories cause the failure. Done means confirming or ruling out the suspected cause and documenting the outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100