diff options
| author | Hans Anderson <me@hansanderson.com> | 2014-12-05 01:36:48 +0100 |
|---|---|---|
| committer | Hans Anderson <me@hansanderson.com> | 2014-12-05 01:36:48 +0100 |
| commit | 3c71f44c6cc26dfe655298b66defdf4890bf6d8b (patch) | |
| tree | 92b9caf79999b02f9756d886237fdbf1e96bb818 | |
| parent | 0972c2194e1bd66e6a399c61c31da68333db426e (diff) | |
Fixed sub-section header
Signed-off-by: Hans Anderson <me@hansanderson.com>
| -rw-r--r-- | contributing.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/contributing.md b/contributing.md index 99ed85909..126bdc74f 100644 --- a/contributing.md +++ b/contributing.md @@ -79,7 +79,9 @@ Hard way The best way to contribute is to "clone" your fork of CodeIgniter to yo The Reactor Engineers will now be alerted about the change and at least one of the team will respond. If your change fails to meet the guidelines it will be bounced, or feedback will be provided to help you improve it. -Once the Reactor Engineer handling your pull request is happy with it they will merge it into develop and your patch will be part of the next release. Keeping your fork up-to-date +Once the Reactor Engineer handling your pull request is happy with it they will merge it into develop and your patch will be part of the next release. + +### Keeping your fork up-to-date Unlike systems like Subversion, Git can have multiple remotes. A remote is the name for a URL of a Git repository. By default your fork will have a remote named "origin" which points to your fork, but you can add another remote named "codeigniter" which points to `git://github.com/bcit-ci/CodeIgniter.git`. This is a read-only remote but you can pull from this develop branch to update your own. @@ -89,4 +91,4 @@ If you are using command-line you can do the following: 2. `git pull codeigniter develop` 3. `git push origin develop` -Now your fork is up to date. This should be done regularly, or before you send a pull request at least.
\ No newline at end of file +Now your fork is up to date. This should be done regularly, or before you send a pull request at least. |