Skip to content

fix: clone spack to specific commit - #49

Open
wdconinc wants to merge 1 commit into
spack:mainfrom
wdconinc:patch-6
Open

fix: clone spack to specific commit#49
wdconinc wants to merge 1 commit into
spack:mainfrom
wdconinc:patch-6

Conversation

@wdconinc

Copy link
Copy Markdown
Contributor

This PR modifies the update script to use a specific commit to avoid unintended breakage through changes in core. We can't write outside GITHUB_WORKSPACE with regulars like actions/checkout, so this remains a run step. We don't have weekly tags on spack/spack anymore, so this is a commit hash with date as comment.

Copilot AI review requested due to automatic review settings July 28, 2026 15:13

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

Pins the Spack clone used by the scheduled UI/package-data update workflow to a specific upstream commit, reducing the risk of unexpected breakages from changes on Spack’s default branch.

Changes:

  • Clone Spack and hard-reset it to a fixed commit hash (with date comment) before running the update script.

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

Comment on lines 15 to +18
- name: Clone development branch of spack
run: git clone https://github.com/spack/spack /opt/spack
run: |
git clone https://github.com/spack/spack /opt/spack
git -C /opt/spack reset --hard e2c5745352ebc0465ebc8d548e60759f05173c83 # Jul 28, 2026
@wdconinc

Copy link
Copy Markdown
Contributor Author

Maybe could use:

[remote "origin"]
  ...
  fetch = +refs/snapshots/*:refs/remotes/origin/snapshots/*

then

git fetch origin snapshots/develop-2026-07-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