Repository navigation
ci: authenticate git push in benchmark README update step - #274
Merged
Merged
Conversation
Cysharp/Actions checkout now forces persist-credentials: false, so the "Update README.md benchmark report link" step failed at git push with "could not read Username". Set GH_TOKEN and run `gh auth setup-git` before pushing. Also pass -NoNewline to Set-Content so README.md does not gain an extra trailing newline on every run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
Benchmark(Default)workflow has been failing at the last step, "Update README.md benchmark report link". The benchmarks themselves complete, butgit pushcannot authenticate:(e.g. https://github.com/Cysharp/ZLinq/actions/runs/40667597126)
The cause is that
Cysharp/Actions/.github/actions/checkoutnow forcespersist-credentials: false(Cysharp/Actions@ecdbb35), so no token is left in the git config even though the job hascontents: write. The last successful Default run (2026-04-08) predates that change.Changes
GH_TOKEN: ${{ github.token }}to the step and rungh auth setup-gitright beforegit push. The shared checkout action is left as is.-NoNewlinetoSet-Content.Get-Content -Rawkeeps the trailing newline, so writing it back without-NoNewlineadded one extra newline to README.md on every run.Notes
Benchmark(Default)onmainafter merge.mainis protected by branch protection or a ruleset, pushes fromgithub-actions[bot]may still be rejected.🤖 Generated with Claude Code