project-chip / project-chip/alchemy
Merge Guard Issues
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 12
- Avg merge
- 23h 54m
- Merged PRs (30d)
- 1
Description
- When no adoc is modified, do not skip commenting. Instead, a no-error comment shall be published.
- Switching to disco-ball-style commenting from the GitHub workflow file using
refresh-message-position: truewould improve timeline clarity. - For the table in comment containing file names, link them to the file.
- In the table, where a link to a specific line in a file exists, if the file hasn't been modified in this PR, link it to the file in the specified branch instead of the "files changed" version.
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 locating the GitHub workflow file and the merge-guard comment generation entry point. Review how no-adoc changes, message positioning, file links, and unchanged-file line links are handled. Done means all four listed comment behaviors work as described; the payload names no tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100