You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`buildcache`| Enable the GitHub Action build cache |`true`|
12
+
|`color`| Force color output |`true`|
13
+
|`path`| Path to install Spack to |`"spack"`|
14
+
|`repository`| GitHub repository for Spack |`"spack/spack"`|
15
+
|`packages_repository`| GitHub repository for Spack packages |`"spack/spack-packages"`|
16
+
|`packages_path`| Path to install Spack packages repository |`"spack-packages"`|
17
+
|`packages_ref`| Version of Spack packages |`"develop"`|
18
+
19
+
## How It Works
20
+
21
+
Spack v1.x uses separate repositories: `spack/spack` (the core) and `spack/spack-packages` (the package repository). This action automatically clones both repositories and configures them using `spack repo set --destination <clone dir> builtin`.
15
22
16
23
## Example: basic setup
17
24
@@ -23,8 +30,8 @@ jobs:
23
30
- name: Set up Spack
24
31
uses: spack/setup-spack@v2
25
32
with:
26
-
ref: develop # Spack version (examples: develop, releases/v0.23)
0 commit comments