Skip to content

Change checkout reference from 'stable' to 'dev'#2

Merged
hverhelst merged 1 commit intomainfrom
hotfix/checkout-gismo-in-dev
Mar 3, 2026
Merged

Change checkout reference from 'stable' to 'dev'#2
hverhelst merged 1 commit intomainfrom
hotfix/checkout-gismo-in-dev

Conversation

@hverhelst
Copy link
Member

No description provided.

Copilot AI review requested due to automatic review settings March 3, 2026 14:44
Copy link

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

Updates the CI workflow to check out the gismo/gismo dependency from the dev ref instead of stable, aligning CI builds with the upstream development branch.

Changes:

  • Switch gismo/gismo checkout ref from stable to dev in the GitHub Actions CI workflow.
Comments suppressed due to low confidence (2)

.github/workflows/ci.yml:30

  • ref: dev makes CI depend on a moving upstream branch, which can make builds non-reproducible and cause unrelated CI breakages when gismo/gismo changes. If the intent is stability, consider pinning to a tag or a specific commit SHA (or documenting why tracking dev is required).
          repository: gismo/gismo
          ref: dev
          path: ./gismo

.github/workflows/ci.yml:27

  • Using actions/checkout@master is risky because it tracks a mutable branch and can change unexpectedly (supply-chain / breakage risk). Prefer pinning to a stable major version (e.g., actions/checkout@v4) or a full commit SHA.
      - uses: actions/checkout@master
        with:

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

@hverhelst hverhelst merged commit 6df8e6e into main Mar 3, 2026
7 checks passed
@hverhelst hverhelst deleted the hotfix/checkout-gismo-in-dev branch March 3, 2026 15:25
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.

2 participants