Issues with the GNU Commit Format Checker
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 231
- Avg merge
- 19h 55m
- Merged PRs (30d)
- 67
Description
With https://github.com/Rust-GCC/gccrs/pull/1850 (but not specific to that one, I would assume) I've observed some issues with the "GNU Commit Format Checker": https://github.com/Rust-GCC/gccrs/actions/runs/4164987612/usage.
The check-changelogs and check-commit-signoff jobs take more than seven minutes, each. That seems a very long time (for what they're doing)? Most of the time is spent in Run actions/checkout@v3. Is that normal?
The check-gccrs-prefix job very quick to execute, but just prints: fatal: not a git repository (or any of the parent directories): .git (but still exits successfully?), so something's wrong there, too.
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 with the GNU Commit Format Checker workflow and the linked actions/checkout run, focusing on the check-changelogs, check-commit-signoff, and check-gccrs-prefix jobs. Reproduce the reported behavior and inspect their checkout and Git context; done means the long-running jobs are appropriately fast and the prefix check no longer reports a missing repository while succeeding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100