js-org / js-org/js.org-cleanup
Cleanup: Post in most recent request PR during automatic contact
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 12
- Forks
- 3
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
For subdomains where we could not, or failed to, create an issue in the target repository, we should instead locate the most recent PR in the js.org repository for the subdomain and leave a comment there using the same body that we use for the issues currently.
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 tracing the automatic-contact path in the cleanup scripts, especially where issues are created and their message body is assembled. Verify how the most recent js.org PR for a subdomain can be located; done means failed issue creation falls back to commenting on that PR with the existing issue body.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript, nodejs
- Domain
- backend, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100