GitHub for Windows
|
06-05-2013, 07:09 PM
(This post was last modified: 07-01-2013 01:31 PM by vnctdj.)
Post: #1
|
|||
|
|||
GitHub for Windows
I encounter an issue with the GitHub's software for Windows.
It happens when I try to sync the commits as you can see on this screenshot : What should I do to bypass this problem ? ♦ Intel Core i7-6700HQ | 16 GB RAM | NVIDIA GeForce GTX 960M | Debian Testing ♦ Intel Core i7-2630QM | 4 GB RAM | NVIDIA GeForce GT 540M | Debian Testing ♦ PSP-3004 | 6.60 PRO-C2 |
|||
06-05-2013, 07:10 PM
Post: #2
|
|||
|
|||
RE: GitHub for Windows
Open a shell and type "git status", it should tell you more about what could be wrong.
-[Unknown] |
|||
06-05-2013, 07:17 PM
Post: #3
|
|||
|
|||
RE: GitHub for Windows
(06-05-2013 07:10 PM)[Unknown] Wrote: Open a shell and type "git status", it should tell you more about what could be wrong. Thanks for your reply I typed "git status" and I got this : What should I do to sync all the commits now ? ♦ Intel Core i7-6700HQ | 16 GB RAM | NVIDIA GeForce GTX 960M | Debian Testing ♦ Intel Core i7-2630QM | 4 GB RAM | NVIDIA GeForce GT 540M | Debian Testing ♦ PSP-3004 | 6.60 PRO-C2 |
|||
06-06-2013, 03:54 AM
Post: #4
|
|||
|
|||
RE: GitHub for Windows
This means that your editor changed the *.vcxproj files. Probably you upgraded them. The easiest thing to do is (from that shell):
git checkout Common Core GPU UI ext Windows headless unittest cd native && git checkout native.vcxproj && cd .. This will reset everything. Another option you have is committing your changes, but you may end up with conflicts that way. -[Unknown] |
|||
06-06-2013, 08:58 PM
Post: #5
|
|||
|
|||
RE: GitHub for Windows
Thanks for taking time to help me
Apparently "git checkout Common Core GPU UI ext Windows headless unittest" did nothing And "cd native && git checkout native.vcxproj && cd .." gave me an error with the "&&" I really don't understand And now I get this when I type "git status" : ♦ Intel Core i7-6700HQ | 16 GB RAM | NVIDIA GeForce GTX 960M | Debian Testing ♦ Intel Core i7-2630QM | 4 GB RAM | NVIDIA GeForce GT 540M | Debian Testing ♦ PSP-3004 | 6.60 PRO-C2 |
|||
06-07-2013, 12:14 AM
Post: #6
|
|||
|
|||
RE: GitHub for Windows
Wait, now they are marked ready to be committed?
git reset HEAD Common Core GPU UI Windows ext headless unittest git checkout Common Core GPU UI Windows ext headless unittest Sorry, forgot it was PowerShell, but seems like native is okay now anyway. -[Unknown] |
|||
06-07-2013, 01:09 PM
Post: #7
|
|||
|
|||
RE: GitHub for Windows
(06-07-2013 12:14 AM)[Unknown] Wrote: Wait, now they are marked ready to be committed? I finally succeed in fixing my problem thanks to your help ! Thank you very much [Unknown], and excuse me about my ignorance, I'm a beginner in all that stuff ♦ Intel Core i7-6700HQ | 16 GB RAM | NVIDIA GeForce GTX 960M | Debian Testing ♦ Intel Core i7-2630QM | 4 GB RAM | NVIDIA GeForce GT 540M | Debian Testing ♦ PSP-3004 | 6.60 PRO-C2 |
|||
06-08-2013, 08:38 PM
Post: #8
|
|||
|
|||
RE: GitHub for Windows
Running all these should give you a pristine state again:
git clean -dfx git submodule foreach git clean -dfx git reset --hard HEAD git pull origin master (run this if you want the latest) git submodule update --init --recursive |
|||
06-08-2013, 08:52 PM
Post: #9
|
|||
|
|||
RE: GitHub for Windows
(06-08-2013 08:38 PM)Orphis Wrote: Running all these should give you a pristine state again: Thanks ! ♦ Intel Core i7-6700HQ | 16 GB RAM | NVIDIA GeForce GTX 960M | Debian Testing ♦ Intel Core i7-2630QM | 4 GB RAM | NVIDIA GeForce GT 540M | Debian Testing ♦ PSP-3004 | 6.60 PRO-C2 |
|||
06-09-2013, 07:10 AM
(This post was last modified: 06-09-2013 05:44 PM by vnctdj.)
Post: #10
|
|||
|
|||
RE: GitHub for Windows
I don't know why, but the problem still appear...
I have to use the commands provided by Orphis each time i want to sync my files ♦ Intel Core i7-6700HQ | 16 GB RAM | NVIDIA GeForce GTX 960M | Debian Testing ♦ Intel Core i7-2630QM | 4 GB RAM | NVIDIA GeForce GT 540M | Debian Testing ♦ PSP-3004 | 6.60 PRO-C2 |
|||
« Next Oldest | Next Newest »
|