![]() As it is right now, I have to tell people to make sure they commit before checking out another branch every single time, which is going to pollute our history, but there's no way I can get the entire team that's already reluctant to use proper source control to use a terminal just to stash before every checkout. It seems to me some sort of stash is a core feature required to even use git, so I'm not sure what other features would be more important to add first. ![]() You want to talk about confusing new users? How about bringing changes over from one branch to a new one silently so they accidentally commit unfinished changes to the wrong branch!? This has already happened on our first day!_ I know this is how git works by default, but in my opinion it's one of the core deficiencies with git, and every other git gui I've ever used prompts you to stash before every checkout to circumvent that.Įither there needs to be a magic stash or a manual stash with a prompt to stash every time you switch branches whether git errors or not. It's like choosing to keep a huge issue because you don't want to address a significantly smaller issue the solution would create. The problem is, the current functionality is horrible and much worse than the problems listed above with magic stashing. I'm trying to transition a group of programmers to git that have little experience in source control. I've got to add my support to magic stashing as well - whether in the old form or some new form. That's on our roadmap, but we can cover the other parts of this feature request in the meantime. I also think this feature depends on us making Desktop better at handling the merge conflicts that may arise from applying stashes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |