Skip to content

fix: use vars instead of env (not available at this point) #307

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

Merged
merged 1 commit into from
Apr 4, 2025

Conversation

jmeridth
Copy link
Member

@jmeridth jmeridth commented Apr 4, 2025

Pull Request

Proposed Changes

Readiness Checklist

Author/Contributor

  • If documentation is needed for this change, has that been included in this pull request
  • run make lint and fix any issues that you have introduced
  • run make test and ensure you have test coverage for the lines you are introducing
  • If publishing new data to the public (scorecards, security scan results, code quality results, live dashboards, etc.), please request review from @jeffrey-luszcz

Reviewer

  • Label as either fix, documentation, enhancement, infrastructure, maintenance or breaking

@jmeridth jmeridth self-assigned this Apr 4, 2025
@Copilot Copilot AI review requested due to automatic review settings April 4, 2025 06:34
@jmeridth jmeridth requested a review from a team as a code owner April 4, 2025 06:34
@jmeridth jmeridth merged commit be8b0fd into main Apr 4, 2025
9 checks passed
@jmeridth jmeridth deleted the jm_use_correct_vars branch April 4, 2025 06:34
@github-actions github-actions bot added the fix label Apr 4, 2025
Copy link

@Copilot 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

This pull request fixes an issue by replacing environment variable references with available workflow variables.

  • Updated the display text in the job name to use github.ref instead of github.event.release.tag_name.
  • Modified the checkout step to reference the tag using github.event.inputs.TAG_NAME with a fallback to github.ref.

Tip: Copilot only keeps its highest confidence comments to reduce noise and keep you focused. Learn more

@@ -13,14 +13,14 @@ permissions:
contents: write
jobs:
update_tag:
name: Update the major tag to include the ${{ github.event.inputs.TAG_NAME || github.event.release.tag_name }} changes
name: Update the major tag to include the ${{ github.event.inputs.TAG_NAME || github.ref }} changes
Copy link
Preview

Copilot AI Apr 4, 2025

Choose a reason for hiding this comment

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

Ensure that using github.ref as a fallback returns the expected tag value in all event contexts, as the semantics of github.ref may differ from github.event.release.tag_name.

Copilot uses AI. Check for mistakes.

runs-on: ubuntu-latest
steps:
- name: Checkout Repo
uses: actions/[email protected]
with:
fetch-tags: true
ref: ${ TAG_NAME }
ref: ${{ github.event.inputs.TAG_NAME || github.ref }}
Copy link
Preview

Copilot AI Apr 4, 2025

Choose a reason for hiding this comment

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

Verify that the fallback to github.ref provides the appropriate branch or tag reference for the checkout process in all workflow scenarios.

Suggested change
ref: ${{ github.event.inputs.TAG_NAME || github.ref }}
ref: ${{ env.BRANCH_OR_TAG_REF }}

Copilot uses AI. Check for mistakes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant