Pantheon workflows: only deploy to prod/staging when content files are modified #5939
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.
Purpose of this pull request
This pull request updates the Pantheon workflow files to ignore changes to files that have no impact on site generation (ex:
README.md,.clabot,CONTRIBUTING.md).I did not include build-related files like
package.jsonanddocusaurus.config.jsbecause changing the build process itself felt like something that should trigger a deployment workflow. If this is inaccurate, and we don't want builds to run when the build tool is updated, I'm happy to amend.Minor housekeeping--this PR also removes the
on:workflow_dispatchevent from the Pantheon workflows. This was left in place from workflow development by mistake.Select the type of change
Ticket (if applicable)
Asana task