Prevent GitHub workflow "tag, release and publish" to be executed automatically, which kind of "disables" it #291
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR properly "disables" our GitHub workflow "tag, release and publish".
It is true the workflow was already disabled in #278 , but not correctly.
The workflow is still existing, but with no content, which is an invalid syntax for GitHub workflows.
Because of that, we are constantly getting the same error over and over:
https://github.com/DazzlingFugu/ember-slugify/actions/workflows/tag-release-publish.yml
We have 2 alternatives here:
To disable the workflow via GitHub web interface
a. On this page https://github.com/DazzlingFugu/ember-slugify/actions/workflows/tag-release-publish.yml
b. Click the
...
button in the top right corner > Disable workflowTo make sure the workflow can only be triggered manually (which is defined by the syntax
on: workflow_dispatch
in the YAML file)This kind of "disables" the workflow as it won't be executed automatically anymore.
There is no syntax to "really disable" a workflow. (like
is_disabled: true
for instance)See:
I went for option (2) so we can actually track this change, to see what happened to the workflow.
With option (1), one could not easily know why the workflow does not run.