[jsword-devel] Hindi bible book names

Matěj Cepl mcepl at redhat.com
Fri Nov 9 13:05:46 MST 2012


On Fri, 2012-11-09 at 12:51 -0500, DM Smith wrote:
> Would you provide a walk-through of the best practices of creating a
> branch, making a change to the branch, and creating/submitting a pull
> request?

1) create an account on Github and login
2) Go to https://github.com/crosswire/jsword/fork (button Fork) and wait
until fork is done
3) clone that repo, e.g., something like
   git clone git at github.com:yourusername/jsword.git
4) cd jsword
5) git checkout -b name-of-new-branch master
6) edit, edit, compile, edit, ...
7) git commit -a -v
   In the text editor you get, review the diff below to be sure,
everythng  is as it supposed to be, and on the top of the file write a
brief explanatory commit message in the format

one-line-not-more-than-80-chars-as-a-headline

Longer explanation of changes you've made (could be many lines long, but
it keep lines under 80 characters each).

8) Save the commit message and leave the editor
9) git push origin name-of-new-branch
10) Go to
https://github.com/yourusername/jsword/tree/name-of-your-branch (switch
branches)
11) and then https://github.com/yourusername/jsword/pull/new/master
(create a new pull request)

The same thing can be done from many IDEs with some GUI stuff, but it is
hard to explain in email.

Best,

Matěj

-- 
http://www.ceplovi.cz/matej/, Jabber: mcepl<at>ceplovi.cz
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
 
Our lives are spectacles of powerlessness.
    -- Richard Rohr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
URL: <http://www.crosswire.org/pipermail/jsword-devel/attachments/20121109/1c194b58/attachment.sig>


More information about the jsword-devel mailing list