Cina Saffary 2b7ed1316d Don't trigger release process when there's no release ... Currently our release process is kicked off whenever a PR is merged and there are no changesets within the `.changeset` directory. Typically this happens when we intend to publish a release, just after we merge a "Version Packages" PR which removes the changesets and adds the entries to our changelog. However, this also means that merging any PR without user-facing changes during the period after we've made a release will trigger another release (which luckily fails because the created tag already exists on the remote. See #184). This change avoids that scenario by fetching tags when checking out the repo. Now when `npx changeset tag` runs, it will see that the tag already exists and skip creating it (`🦋 Skipping tag (already exists): v3.3.2`). The `git push --tags` step will no longer throw an error ("Everything up-to-date"). And lastly, the publish step won't get triggered because the output from `npx changeset tag` doesn't contain the string `"New tag:"`. The action should just finish successfully with nothing to left do. Fixes #184		2023-10-31 10:21:29 -05:00
..
deploy.yml	Refactor to use npm as a fallback if no packageManager specified...	2023-10-09 17:20:09 -05:00
issues.yml	Fix workflow syntax for multiple conditions	2023-10-05 15:29:35 -04:00
pullrequests.yml	Update pullrequests.yml	2023-10-11 15:24:12 +01:00
release.yml	Don't trigger release process when there's no release	2023-10-31 10:21:29 -05:00
workerHealthCheck.cjs	Quiet feature	2023-08-16 09:37:29 -05:00