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
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.
Hello! I and my team are working on a game and have been making regular commits.
We just realized that we have a big bug in a previous version of the game, a version that we use for exhibitions and so on.
So I want to go back to the commit that this version is based on, fix the bug, build a new game version, and then return to the latest commit and keep working.
What should I do? I get confused by all the different options and what they do.
Hello! This will depend on your setup.
Normally whenever you start a new feature, or bug-fix it's advised that you make a new branch for it. Then you'd normally merge that back into the "master" branch when you're done. However, you can also use branches for releases too -- whenever you do a release you should make a new branch from that point so that you can go back and fix things on that branch if needed.
It sounds like you might not have done that (and that's OK!). So here's what I'd recommend you do:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.