summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBrendan Corazzin <brendancorazzin@Brendans-MacBook-Pro.local>2019-05-28 21:43:44 +0200
committerBrendan Corazzin <brendancorazzin@Brendans-MacBook-Pro.local>2019-05-28 21:43:44 +0200
commit2eff8a25cc06f35ae8a5e5efebfc7fa739ed7fae (patch)
treeefb9ef7ca0f452ff4800a9a1eeb722a2d2e5719b
parent73cde1994aad64a32d19d8b2e11f1b82ccaad19d (diff)
Adding back 'git@github.com:<your-name>/CodeIgniter.git' to step 4 in the how-to guide
-rw-r--r--contributing.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributing.md b/contributing.md
index 46ce0190e..8f43c45a6 100644
--- a/contributing.md
+++ b/contributing.md
@@ -69,7 +69,7 @@ Hard way The best way to contribute is to "clone" your fork of CodeIgniter to yo
1. [Set up Git](https://help.github.com/en/articles/set-up-git) (Windows, Mac & Linux)
2. Go to the [CodeIgniter repo](https://github.com/bcit-ci/CodeIgniter)
3. [Fork it](https://help.github.com/en/articles/fork-a-repo)
-4. [Clone](https://help.github.com/en/articles/fetching-a-remote#clone) your forked CodeIgniter repo.
+4. [Clone](https://help.github.com/en/articles/fetching-a-remote#clone) your forked CodeIgniter repo: git@github.com:<your-name>/CodeIgniter.git.
5. Checkout the "develop" branch. At this point you are ready to start making changes.
6. Fix existing bugs on the Issue tracker after taking a look to see nobody else is working on them.
7. [Commit](https://help.github.com/en/articles/adding-a-file-to-a-repository-using-the-command-line) the files