Investigate removing release-notes cron entries from healthz
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start at the healthz cron endpoint and search the repository configs for release-notes and wmo references. Check whether the job is used elsewhere before removing obsolete entries; done means no leftover release-notes cron configuration remains and relevant tests or checks pass.
Written by the indexing model from the issue text.
Description
Description
Release Notes are no longer served from wmo. The cron endpoint should not list that job.
Success Criteria
- No leftovers esp. if otherwise unused
- Remove from configs if no longer run
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 974
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 21
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.
More from mozilla/bedrock
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Enhancement Frontend P3 Quick
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Help wanted
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Frontend L10N
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getgrav/grav-plugin-api#45 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·