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.
Pay attention to this code review as it would tweak the process and this needs to be discussed.
Changes summary
bitbucket-pipelines.yml
package.sh
merge.sh
prepareRollbackBranch.sh
Overview:
Going forward, when we deploy a pull request it will perform a merge and squash.
This will make it easier to do a revert in the future.
There is a new custom pipeline that allows for us to specify the commit hash we want reverted.
The custom pipeline will run and create a new pull request that is a revert of the provided hash.
All pull requests that start with rollback/ will automatically build the package and validate the package.
The only thing the user will need to do is click "Deploy Rollback".
Process change
Because we are making Bitbucket API calls, there is a need for workspace variables
The app password needs to include the ability to write pull requests.
The above two variables are technically already in the bitbucket pipeline yaml file (reference $tests).
We would need to update the documentation on the pipeline b/c the above to variables are not documented there to begin with.