rajbos / rajbos/github-fork-updater
Check if the update also means new tags / releases
Open
Nobody has claimed this yet.
request
- Dominant language
- PowerShell
- Stars
- 19
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
Especially when used with version tags (like GitHub Actions), it is helpful to see the incoming tags in the comment that is generated. That can indicate breaking changes that might need extra scrutiny.
Annotate the body with the create issue
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
Start by locating the code that generates the update comment and handles version tags, then inspect how the issue body is annotated. Done means the generated comment exposes incoming tags or releases clearly enough to flag possible breaking changes, with the requested create-issue annotation preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, powershell
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100