-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
autoupdater to keep git up-to-date #1256
Comments
Wouldn't it? It would be as fantastic as a contribution adding this feature! 😄 |
This might be an option to integrate here: https://github.com/ravibpatel/AutoUpdater.NET |
When I said "contribution", I did not mean "throw a random link at the Git for Windows maintainer who is busy releasing an emergency release". |
I use this function.
UPDATE 2:
UPDATE 1:
Usasge
Output when up to date with latest version
Output when not on the latest version
|
@dscho I'm very sorry! Just provided that link because I think this might be an option to implement this. I'm willing to contribute be my self or via some of my co-workers. However, I have to get familiar with the code base and installer creation first. |
@between2spaces that's a nice script! A couple of suggestions:
|
Indeed, nice script @between2spaces . You could launch the installer and kill the Git bash like this: start "" "path/to/installer"
ps | grep mintty | awk '{print "kill -9 " $1 ";" }' | sh |
Nice command-line, but please keep in mind that Git Bash can be configured to be run via ConHost instead of MinTTY. |
Thanks for your kind words. I've taken on board @dscho 's suggestions and updated the script (see previous post for the updated script).
UPDATE: I seem to have solved the auto run using @larsxschneider's suggestion . Thought the issue about 'mintty' not always being the correct process to kill is something I'm unsure what to do about. |
@between2spaces how about putting this under version control, e.g. into https://github.com/git-for-windows/build-extra/tree/master/git-extra? |
@dscho Would this be more general?
Here I grep for |
@between2spaces I'd suggest making the internal variables local, to avoid inadvertently clobbering items which were set outside of the function.
|
@dscho Probably a good idea to put it somewhere. Is build-extra the right spot? I don't have or intend to use build-extra's. @landstander668 Awesome. Thanks for the improvements. I've updated the function. @larsxschneider Good idea. I tried your parent of bash idea and it seems to work. I've incorporated it into the updated function. |
We are using chocolatey for managing our tools. 😃 |
I downgraded to version 2.13.3 just so I could give @between2spaces's function a try. It worked beautifully. 🥇 |
I specifically pointed to the In any case, you already see from comments like this one that you need to put this script under version control ASAP so you can accept Pull Requests. |
Done. Pull request git-for-windows/build-extra#151 Thanks for the explanation @dscho on what git-extra is for. I was aware of that. |
So, @bufferoverflow... a lot of your wish has already been fulfilled by others. How about giving it some love, walk the last inches of the whole nine yards and teach |
@dscho I will do so, my local installer asks already Daily check for available update during postinstall and a daily schtasks will then be created. |
Just to clarify: I was suggesting to thank @between2spaces, @viceice, @landstander668 and @larsxschneider by contibuting a Pull Request that adds this option to Git for Windows' installer... I am not sure you were talking about that installer because it does not have a "Daily check for available update" function. |
Dear @dscho, @between2spaces, @viceice, @landstander668 and @larsxschneider thank you so much for the |
@dscho did some enhamcements on my second PR which uses git |
Thanx a lot to everyone who made this possible!!! Specially @bufferoverflow who triggered this. |
hey folks! in a discussion on Twitter @gbraad wrote that As an alternative I think |
Hey all! @larsxschneider @gbraad To be sincere, I believe the best would be to trigger the update automatically by default and just ask the user if he/she wants to do it now or later. The window asking should say something like: "git client has a new version, would you like to update it now or later?" I mean this is only for the Windows client, so it would be more comfortable to have a real pop-out window asking. |
I think that would be a separate discussion. I really like the explicit command for the upgrade as changing the version control system can have a severe impact (e.g. some workflows don't work anymore because of the new version of something). |
I proposed the change here in a PR: git-for-windows/build-extra#167 |
ok, you are right, I agree and I believe most of the people would! |
Thanks! Good to see this being picked up... |
Setup
Details
The text was updated successfully, but these errors were encountered: