Skip to content

ci: skip release-please job when secret is not defined#66

Closed
Copilot wants to merge 1 commit intomainfrom
copilot/replicate-changes-from-pr-59
Closed

ci: skip release-please job when secret is not defined#66
Copilot wants to merge 1 commit intomainfrom
copilot/replicate-changes-from-pr-59

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Apr 18, 2026

The release-please workflow errors in forks or environments where RELEASE_PLEASE_TOKEN_PROVIDER_PEM is not configured, failing at the GitHub App token generation step.

Changes

  • .github/workflows/release-please-gha.yml: Added an if condition to skip the release job when the secret is absent:
jobs:
  release:
    if: ${{ secrets.RELEASE_PLEASE_TOKEN_PROVIDER_PEM != '' }}

Mirrors the fix in kiota-http-ruby#59.

@baywet baywet marked this pull request as ready for review April 18, 2026 10:41
@baywet baywet requested a review from a team as a code owner April 18, 2026 10:41
@baywet baywet requested a review from Copilot April 18, 2026 10:42
@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Skips the Release Please job in environments (e.g., forks) where the GitHub App private key secret is not configured, preventing workflow failures during token generation.

Changes:

  • Add a job-level if guard to only run the release job when RELEASE_PLEASE_TOKEN_PROVIDER_PEM is non-empty.

@baywet baywet closed this Apr 20, 2026
auto-merge was automatically disabled April 20, 2026 12:39

Pull request was closed

@baywet baywet deleted the copilot/replicate-changes-from-pr-59 branch April 20, 2026 12:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants