Skip to content
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

Submodules improvements #2161

Closed
signumsoftware opened this issue Dec 5, 2013 · 1 comment
Closed

Submodules improvements #2161

signumsoftware opened this issue Dec 5, 2013 · 1 comment

Comments

@signumsoftware
Copy link

We're constantly using and updating sub-modules but the git implementation, based in references to SHA1, while correct, is hard to work with if you make changes in the sub-module often.

Some improvements that i think GitExtensions could have:

Show parent branches

When in a sub-module, GitExtensions underscores the commit witch the super repository is pointing to. This is good but not enough. I would like to see a yellow decorator, like the red for local banches, green for remote branches and blue for tags, that represents the version of each branch in the super repository. This decorator could be grayed out because it makes no sense to check it out but still is a valuable peace of information.

Show commit changes when committing sub-module reference updates

When the super repository updates a sub-module, now there are beautiful arrows indicating whether you're upgrading or downgrading it. It will be even better if it indicates how many commits you're upgrading and/or downgrading. Knowing this information will be useful to avoid confusing unintended library updates to 'just my change' updates.

Show commit changes when checking out branches from [no branch]

When you're in a sub-module (usually in [no branch]) and you want to commit, a dialog asks you to checkout a branch. Knowing how far away it is will be useful to prevent unintended checking out of far in the future versions.

  • You think those are good changes on GitExtensions?
  • If implemented properly will eventually go to master?
  • Some advice about how to implement them?
@KindDragon
Copy link
Contributor

Done in 2.48

@KindDragon KindDragon added this to the 2.48 milestone Sep 1, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants