-
-
Notifications
You must be signed in to change notification settings - Fork 601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to follow config push settings #2537
Comments
Same issue on Seems like repo config
I guess we should consider "can" as "should" for GitUI |
I don't want to discuss what's better or worse, but I've been looking at #2542 and was confused until I saw this:
While this is probably a configuration ( The current gitui behavior seems to be Instead, git by default refuses such pushes in Would it be reasonable to check |
@naseschwarz Hey!
From git-config(1):
Key point is This issue & my PR fix is addressing the case, when refspec is configured, What you are referring to is a fallback scenario, when no refspec Arguing about best |
I don't think
Even though |
Because you explicitly specified
Do push with |
To clarify: I didn't checked that Considering that i would say logic should be: |
I mostly agree, except: As git defaults to Ultimately, this is not up to me, though. I'm new here. ;) |
You are totally right with So thank you a lot for heads up :) |
Describe the bug
I'm working on a repo with multiple remotes (origin and fork) and have a branch locally with different name which pushes to
main
branch on the forkTo Reproduce
.git/config
in
.git/config
Expected behavior
when executing
git push --verbose
on such branchScreenshots
N/A
Context (please complete the following information):
Rust: cargo 1.84.0 (66221abde 2024-11-19) (stable)
gitui: 0.27.0
OS: NixOS 25.05 (Warbler) x86_64
Host: Windows Subsystem for Linux - NixOS (2.4.11)
Kernel: Linux 5.15.167.4-microsoft-standard-WSL2
Shell: bash 5.2.37
Additional context
As noted in the logs this is a gitlab instance if that changes things
The text was updated successfully, but these errors were encountered: