Skip to content

Set release persist-credential false#82

Merged
5ouma merged 1 commit into
mainfrom
ci-release-persist-credential-false
Jun 9, 2026
Merged

Set release persist-credential false#82
5ouma merged 1 commit into
mainfrom
ci-release-persist-credential-false

Conversation

@5ouma

@5ouma 5ouma commented Jun 9, 2026

Copy link
Copy Markdown
Owner

⚠️ Issue

close #


✏️ Description

Set the GitHub CLI as a Git credential helper to operate.


Set GitHub CLI as a Git credential helper to operate.
Copilot AI review requested due to automatic review settings June 9, 2026 14:09
@github-actions github-actions Bot added the 🎽 CI Changes to CI configuration files and scripts label Jun 9, 2026
@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@5ouma, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 37 minutes and 1 second. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 01500683-a4ec-431d-a0bf-f91a053ca882

📥 Commits

Reviewing files that changed from the base of the PR and between dd5ac81 and b55145c.

📒 Files selected for processing (2)
  • .github/ghalint.yml
  • .github/workflows/release.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci-release-persist-credential-false

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the release workflow to avoid persisting checkout credentials and instead rely on GitHub CLI as the Git credential helper during the tagging/release process.

Changes:

  • Set actions/checkout persist-credentials: false for the tagpr job and configure Git credential handling via gh auth setup-git.
  • Provide GH_TOKEN to the tagpr action environment for GitHub CLI/API authentication.
  • Remove the ghalint exclusion related to checkout_persist_credentials_should_be_false.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
.github/workflows/release.yml Switches checkout to non-persistent credentials and adds GitHub CLI credential helper setup for the release tagging flow.
.github/ghalint.yml Removes the previous linter exclusion tied to persist-credentials.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/release.yml
@5ouma 5ouma merged commit e99d586 into main Jun 9, 2026
8 checks passed
@5ouma 5ouma deleted the ci-release-persist-credential-false branch June 9, 2026 14:13
@5ouma 5ouma Bot mentioned this pull request Jun 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🎽 CI Changes to CI configuration files and scripts

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants