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
If you have a custom Composer filename, you may use `composer-filename` to change
91
+
the filename Composer uses. For example, your Composer file could be
92
+
`composer-gh-actions.json`or `composer-staging.json` instead of the default
93
+
`composer.json`.
94
+
95
+
You should specify the filename without the extension, since it will determine
96
+
both the JSON and lock filenames to use. The default value is `"composer"`,
97
+
which will use `composer.json` and `composer.lock` as the filenames.
98
+
99
+
For example:
100
+
101
+
```yaml
102
+
- uses: "ramsey/composer-install@v3"
103
+
with:
104
+
custom-composer-filename: "composer-gh-actions"
105
+
```
106
+
88
107
#### working-directory
89
108
90
109
The `working-directory` input parameter allows you to specify a different
@@ -120,6 +139,8 @@ For example:
120
139
121
140
#### ignore-cache
122
141
142
+
Normally, ramsey/composer-install preserves composer's cache between jobs
143
+
so that subsequent identically-invoked jobs execute faster.
123
144
If you have jobs for which you wish to completely ignore the caching step, you
124
145
may use the `ignore-cache` input parameter. When present, ramsey/composer-install
125
146
will neither read from nor write to the cache.
@@ -175,6 +196,17 @@ even more specific, you can specify a suffix to be added to the cache key via th
175
196
> [!WARNING]
176
197
> Specifying a `custom-cache-key` will take precedence over the `custom-cache-suffix`.
177
198
199
+
200
+
#### require-lock-file
201
+
202
+
By default, if no composer.lock file is found in the working directory
203
+
ramsey/composer-install will invoke `composer update` regardless of the value of
204
+
`dependency-versions`.
205
+
206
+
If this is set to a value of `true`, ramsey/composer-install will fail in its
207
+
execution if it does not find a lock file.
208
+
209
+
178
210
### Fork and private repositories
179
211
180
212
Sometimes it's needed to use the `repositories` key in your `composer.json` to pull in forks, PRs with patches or private repositories. In this case, your GitHub Action may start failing with a `Could not authenticate against github.com` error message. To solve this, you need to use an authorized token; luckily [GHA provides you with one automatically at each run](https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication), you just need to set the `repository-projects` permission to `read`:
0 commit comments