Archived repos cause notifications to fail?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github
- Domain
- tooling
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.
Description
One of the repositories we had listed in the [email protected] 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.
- Dominant language
- No language data
- Stars
- 17
- Forks
- 38
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from w3c/github-notify-ml-config
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
w3c/github-notify-ml-config#250 ·
-
Tidy up?Open
Difficulty 1/5 Under an hour Newbie friendliness 50/100
w3c/github-notify-ml-config#216 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
w3c/github-notify-ml-config#156 · 2 comments ·
-
add a Travis check that added repos actually existMay be free again @dontcallmedom claimed this 3363 days ago, and no pull request is open. Open
w3c/github-notify-ml-config#92 · 1 assignee ·
All issues in w3c/github-notify-ml-config
Similar issues
-
skillfs: one malformed chat-log line aborts the entire skill-usage analysis (skill_usage_from_chat_logs.py)Possibly taken @zjncs claimed this today. Opencomponent:skillfs
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
agentic-os-org/ANOLISA#6116 · 1 comment ·
Maintainers usually reply within 1 day
-
kwok: shared-cluster runs leak kube-system releases between recipes, failing inventory read-backOpenarea/tests theme/ci-dx
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
FluidNumerics/fluid-walk-blocker#172 ·
Maintainers usually reply within 1 day
-
Forge coverage prompts carry text the agent cannot act onPossibly taken @graalvmbot claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
oracle/graalvm-reachability-metadata#10572 ·
Maintainers usually reply within 1 day