You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Heyyy Forum,
Just wondering whether what we are trying to do here is possible with Bitbucket or not.
Currently, every developer will create a new branch for an issue that they are working on - pretty usual. However, to minimize the team required for review, we centralized any commits from DEV branches to a DEV Heroku application.
This has proven to be a little challenging because as soon as someone commited a change to their dev branch, the heroku app is updated along with the HEAD - and the rest of the team is falling behind causing confusion.
An integrated Github repo and Heroku allows a temporary branch to be created for any dev branch that is created.
Just wondering if such an option exists through Bitbucket as well?