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
We are using an on-premise GitLab repository, which prevents us from utilizing the post-authentication features.
The gs repo sync command works, but only fetches the main branch and encounters the errors outlined in issue #391.
It would be really nice to have a feature that allows for "restacking" a branch to the remote value.
The text was updated successfully, but these errors were encountered:
Sorry, would you clarify, please?
The set up doesn't allow fetching local refs of remote branches? i.e. it doesn't provide feature1, only origin/feature1?
Or is this limitation only for the main branch?
The gs repo sync command only updates the main branch (trunk). It would be nice if it also attempted to fetch all the tracked branches.
Let's imagine I have branch A and branch B where main <-- A <-- B is the hierarchy, and A is pushed to a remote as origin/A. If a change happens to origin/A and I fetch it, I will have a new origin/A branch locally. I would like to 'merge/move' A and the new origin/A together, and rebase B in one command.
We are using an on-premise GitLab repository, which prevents us from utilizing the post-authentication features.
The
gs repo sync
command works, but only fetches the main branch and encounters the errors outlined in issue #391.It would be really nice to have a feature that allows for "restacking" a branch to the remote value.
The text was updated successfully, but these errors were encountered: