Daniel Lockyer aec14e5cf3 Disabled FORCE_COLOR on setup-node GitHub Action ... refs https://github.com/TryGhost/Ghost/pull/13716 refs https://github.com/actions/setup-node/issues/317#issuecomment-929694556 - the `setup-node` GitHub Action seems to use a shell command to get the cache path, but these are colorised when `FORCE_COLOR` is enabled - this causes the Action to fail to read the path correctly - the comment referenced above suggests to remove `FORCE_COLOR` but it's nice to have colored output for our tests - instead, I'm disabling the environment variable on the `setup-node` action so it still works - I've tested with the referenced PR and this unblocks dependency caching 🎉		2021-11-25 09:11:35 +01:00
..
auto-assign.yml	Moved GITHUB_TOKEN env variable to workflow scope	2021-09-09 09:49:08 +01:00
canary.yml	Disabled FORCE_COLOR on setup-node GitHub Action	2021-11-25 09:11:35 +01:00
label-actions.yml	Added issue closed event to triggers for label action	2021-11-18 11:05:49 +01:00
migration-review.yml	Pinned GH Action for migration PR workflow to a specific commit	2021-11-12 15:49:41 +00:00
release.yml	Disabled FORCE_COLOR on setup-node GitHub Action	2021-11-25 09:11:35 +01:00
stale.yml	Update actions/stale action to v4	2021-11-15 08:23:54 +00:00
test.yml	Disabled FORCE_COLOR on setup-node GitHub Action	2021-11-25 09:11:35 +01:00