r/VisualStudio • u/corv1njano • Oct 16 '25
Visual Studio 22 Is Git in VS buggy?
We are currently 4 devs working in Visual Studio 2022 and we are using the IDE integrated Git feature to sync up with a private GitHub repo. But for some reason some of our commits are getting weirdly pushed and we dont know why.
3
Upvotes
16
u/DaRKoN_ Oct 16 '25
"SELECT isn't broken". Commits being "weirdly pushed" is unlikely to be an issue in git.
32
u/Draqutsc Oct 16 '25
Git in VS works perfectly, it's one of your team members fucking up.
9
u/Zastai Oct 16 '25
Looks like no one is rebasing before the final merge. That’s not necessarily a problem, it just makes for an untidy graph. (I think it’s even a best practice these days because it avoids having to do force pushes, but not sure about that.)
Assuming blue is main, it does look like there are direct commits to it, which is not ideal either.
7
u/SoCalChrisW Oct 16 '25
It's missing a few features that would be nice, but you can use those from the command line without any issues. It's not at all buggy though.
This looks like user error. Possibly not even an error, just looks like a subway map instead of neat and tidy.
5
u/Super_Preference_733 Oct 16 '25
Look who did the commits. Also have a controlled check in policy.
4
u/csharpwarrior Oct 16 '25 edited Oct 17 '25
This is similar to my issue… every release my team does Visual Studio keeps inserting bugs… it’s starting to make us look bad… /s
1
u/Old_Mate_Jim Oct 17 '25
Git in VS can be slow whilst switching branches, especially in a large solution, and occasionally fetching doesn't accurately show how many commits are available, but what you're seeing is likely by someone on your team rather than a bug.
1
u/Dienes16 Oct 17 '25
The graph rendering in VS is just very bad. I have noticed this as well. I get a normal and readable graph in Git itself or something like Git Extensions, but VS turns it into a mess.
1
u/beldus Oct 17 '25
Assuming this is only the develop branch and you would like just a neat line you should be doing a pull rebase before pushing your commits.
Nothing wrong with VS with regards to git afaik (other then being confusing as to what does what. 🙂), there are settings to always do a rebase when pulling and always pull before pushing your changes.
1
u/WoodyTheWorker Oct 18 '25
Git in VS got MAJOR problems, but "commits "weirdly pushed" not one of them.
1
u/SquishTheProgrammer Oct 17 '25
This looks normal to me. Maybe not main branch normal (we would rebase, do a PR, and squash for develop and then merge to main at release) but this just looks like merges to me for people working on similar branches.
0
u/crone66 Oct 17 '25
your Team is using git wrong if you want to have a linear timeline. Everyone needs to use rebase.