+1 for branch permissions when using HTTP, somehow.
+1 for branch permissions for CI
is it necessary to have the pipeline fail on a git commit that doesn't have anything to commit?
i guess the simplest workaround everyone is doing is providing an echo output to a file prior?
will this pipeline failure on nothing to commit always behave like this or is there any change in the works?
thx for any info.
-jw
If you don't want a pipeline failure on a git command, use the "OR" operand || to allow the command to return 0:
- git commit -a || echo "Nothing to commit"- git push || echo "Nothing to push"
Pushing back using the http origin to repositories where branch permissions are enabled is not yet supported.
+1 to have this supported as we are using branch permission.
Our current workaround is to switch to SSH before pushing
git remote set-url origin ${BITBUCKET_GIT_SSH_ORIGIN}
Any update regarding the support of pushing back using the http origin with branch permissions enabled?
Linette
Experience Design Manager
7 accepted answers
54 total posts
56 comments