-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with the GNU Commit Format Checker #1853
Comments
It looks like the github checkout action doesn't support checking out a dynamic range of comments - just all/ |
@tschwinge the checkout action does take a lot of time and I'm not sure why. We do the following: - uses: actions/checkout@v3
with:
ref: ${{ github.event.pull_request.head.sha }}
fetch-depth: 0 instead of simply steps:
- uses: actions/checkout@v3 as we do in the other workflows. I'm not sure why haha. Regarding the - uses: actions/checkout@v3
if: ${{ github.base_ref == 'gcc-patch-dev' }} # master commits don't need the gccrs prefix then, in the following step, it sets the retval to 0, tries to loop over commits, fails to get commits, and then exit retval. Which is also why I didn't notice it was broken in the first place :D The list of things to do is thus as follows:
|
https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/ It looks like the github checkout action doesn't support it yet: |
With #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.The text was updated successfully, but these errors were encountered: