Need a step by step instruction (with SCREENSHOTS) how to:

1. Commit code changes back into Git.

Comments

eliza411’s picture

Project: Git on Drupal.org » Documentation
Component: Documentation » Missing documentation
Issue tags: +git phase 3

Moving to the docs queue

arianek’s picture

Issue tags: +git

tags

aspilicious’s picture

Status: Active » Fixed

I believe this is fixed with the updated docs jhodgdon has written. If you still feels this is not enough I'm afraid you have to read some more about git in general and read the egit user guide.

hass’s picture

Status: Fixed » Active

Where are these docs? I have not seen any with screenshots yet

aspilicious’s picture

Priority: Critical » Minor
Status: Active » Fixed

1) not critical, only site braken stuff is critical, please read the guidelines. This is actually minor because people can use egit like they should with the info written. I confirmed this with several people on irc.

2) I guess you can read English, *every* step is explained. We decided to not use any screenshots because it doesn't add any value in this case. (The written steps make everything clear). There is also more info and some screenshots on this page: http://wiki.eclipse.org/EGit/User_Guide#Committing_Changes. (there was a link to the user guide if you read everything carefully).
It is always advised to check that page as it explains everything you need to know about egit

3) If you think you can add some usefull screenshots feel free to make them: http://en.wikipedia.org/wiki/Screenshot.
If you're not planning to help us improve this doc, this issue will be fixed and stay fixed.

jhodgdon’s picture

hass: the page on Eclipse is at http://drupal.org/node/1077484 if you didn't find it

hass’s picture

Followup for this banana software that only make headaches #1106008: How to push tags/branches to d.o

Status: Fixed » Closed (fixed)
Issue tags: -git, -git phase 3

Automatically closed -- issue fixed for 2 weeks with no activity.