You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.
Join groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
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.
Thanks!
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:
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.