I'd like to define and manage a remote symbolic-ref. Is there any way to manage symbolic-refs in the remote repository?
For example, I have an internal process/script that I'd like to configure with a single git reference that points to a branch. Behind the scenes I want to be able to change the reference in Bitbucket to point to another branch and thus allowing me to never change the internal process/script.
Just to clarify - what I want is a way to manage symbolic references.
We have several release branches that "roll" (for lack of a better term). For example, lets say that I have 2.0, 2.1, and 2.2 in the works. We would like our build system to be configured once to get "red", "green" and "blue" where these are references to 2.0, 2.1, and 2.2, respectively. At some point we start 2.3, we release, and we want "red", "green", and "blue" to now reference 2.1, 2.2, and 2.3, respectively. We don't want to reconfigure the build system; instead, we just want to change the symbolic references.
Does that make sense? Is there a better way to go about doing this?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs