Option to make Git Commit GUI look different from TortoiseSVN equivalent
By eric.v.hi... on March 07, 2013 22:10 (imported from Google Code)
- Look at the TortoiseGit commit dialog
- Look at the TortoiseSvn commit dialog
PROBLEM -- they look too similar and it's easy to confuse the two.
The use case here is:
- The organization is using SVN and TortoiseSVN and may not migrate to Git for a while.
- Individual developers have begun to use Git and TortoiseGit locally to allow frequent commits, local branching, etc.
- Code reviews are required when committing to SVN, but not to local Git repositories
- Developers using local Git repositories are committing routinely to their local trunk without worrying about whether their changes are production quality.
- Developers are sometimes accidentally committing huge chunks of local cruft to SVN when they mean to be committing said cruft to Git.
So the feature request is to "Make it harder to to accidentally check in to SVN when you think you're checking in to Git."
Tons of possible implementations: configurable background colors, big obvious watermarks, a major divergence in the UI look and feel between the 2 tools, etc. I personally would be fine with a configurable color option (I use this pattern in my cmd windows as a reminder of which environment I'm working in), but I'm sure there are less hacky approaches as well.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information