nodejs / nodejs/userland-migrations
Automatically create issue when a deprecation PR lands in Core
Open
Nobody has claimed this yet.
gh actions
- Dominant language
- TypeScript
- Stars
- 85
- Forks
- 55
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 9
Description
Currently, we get tagged via Code Owners, so we're at least aware. But I realised we can do much better: We can create a GH Workflow to automatically open an issue in this repo when a deprecation PR lands in nodejs/node.
I spoke with Antoine about where the workflow should live, and it would be better for it to live here (rather than Core).
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.
Research direction
No file or test is named. Start by defining the GitHub Workflow trigger for deprecation PRs in nodejs/node and the permissions needed to open an issue here. Done means a deprecation PR landing in Core causes one correctly populated issue in this repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100