16,736
edits
Changes
From Gramps
→Basic Work Flow
Try to keep your commits digestible and understandable. A large changeset can be broken into several commits that "tell a story" about how the changeset moves the program from its old behavior to its new one.
To push your changes to the Gramps repository, you need to have cloned the Gramps source code with ssh, and have push access to the Gramps repository (the Gramps admins can give you this, [[Contact|Brian Matherly or Benny MalengierNick Hall]]). If you don't have push access continue in the next section below. First update again to make sure that you can fast-forward the repository, then push:
git pull --rebase
The next stop is at github itself. Grab your web browser and navigate to your account and your repository and the 'branches' tab <nowiki>https://github.com/yourname/gramps/branches</nowiki>. You should see your newly 'pushed' branch ('mybranch') listed with a 'New Pull Request' button on the right.
You can then fill out the PR form. You might have to select the Gramps 'base' branch you are basing on if it is different than 'master', this will be evident if you see "Can’t automatically merge". Add any comments you have on your work. And push the 'Create Pull Request' button.
