refactor: remove push to bitbucket workflow #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit removes both the now unnecessary GitHub workflow and BitBucket pipeline. Originally, the BitBucket repo had a pipeline to automatically trigger a deploy of the site in Matrix - so every update in GitHub has to be copied across to BitBucket, where the deploy would then be triggered. Now this trigger is handled in GitHub with a webhook - so copying-and-pasting across to BitBucket is no longer necessary.
injms
force-pushed
the
remove-push-to-bitbucket-action
branch
from
c920ed0 to
143edcd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Remove the GitHub Actions workflow that would push a copy of this repo across to BitBucket.
Why
Originally, the BitBucket repo had a pipeline to automatically trigger a deploy of the site in Matrix - so every update in GitHub has to be copied across to BitBucket, where the deploy would then be triggered.
Now this trigger is handled in GitHub with a webhook - so copying-and-pasting across to BitBucket is no longer necessary.