Skip to content

include.yaml: redirect to ACCESS-NRI's spack-config#30

Merged
harshula merged 1 commit into
releases/v1.1from
test-v1.1
Apr 14, 2026
Merged

include.yaml: redirect to ACCESS-NRI's spack-config#30
harshula merged 1 commit into
releases/v1.1from
test-v1.1

Conversation

@harshula
Copy link
Copy Markdown
Collaborator

@harshula harshula commented Apr 8, 2026

@harshula harshula self-assigned this Apr 8, 2026
@github-project-automation github-project-automation Bot moved this to New Issues 🌅 in Model Release Apr 8, 2026
@harshula harshula changed the base branch from releases/v1.1 to develop April 8, 2026 05:33
@harshula harshula changed the base branch from develop to releases/v1.1 April 8, 2026 05:33
@CodeGat
Copy link
Copy Markdown
Member

CodeGat commented Apr 9, 2026

I will add a commit that clones our spack-config in the above CI that is failing, one sec...
EDIT: It wasn't that simple so I reverted it.

@CodeGat CodeGat force-pushed the test-v1.1 branch 3 times, most recently from 4d61b9c to 278f4dc Compare April 9, 2026 01:45
* Spack CI is failing because it needs access to spack-config repo.
@harshula harshula merged commit 018ccf0 into releases/v1.1 Apr 14, 2026
8 of 11 checks passed
@github-project-automation github-project-automation Bot moved this from New Issues 🌅 to Done ✅ in Model Release Apr 14, 2026
harshula added a commit that referenced this pull request Apr 21, 2026
* Spack CI is failing because it needs access to spack-config repo.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done ✅

Development

Successfully merging this pull request may close these issues.

3 participants