You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if there is a known workflow for checking out an old release branch. For example, in the context of our project, we have some users who are on older versions of the app. But when I apply the old release branch using GitButler, it creates a bunch of merge conflicts for me. The workflow for going "forward" in history is clear to me, but is there a considered workflow for going "backwards", as we need to do this from time to time to create patch releases.
Thanks for your reply and for all the hard work on this awesome tool.
This discussion was converted from issue #3602 on May 14, 2024 08:21.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi there,
I'm wondering if there is a known workflow for checking out an old release branch. For example, in the context of our project, we have some users who are on older versions of the app. But when I apply the old release branch using GitButler, it creates a bunch of merge conflicts for me. The workflow for going "forward" in history is clear to me, but is there a considered workflow for going "backwards", as we need to do this from time to time to create patch releases.
Thanks for your reply and for all the hard work on this awesome tool.
Beta Was this translation helpful? Give feedback.
All reactions