mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-08 07:42:33 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update wikipage Code Templates. (Signed-off-by:javier).

Browse Source 
git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1695 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
eiffel-org
2016-11-23 18:35:56 +00:00
parent 5e1fd9c98e
commit 8f084e54ac
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki
View File

@@ -107,7 +107,7 @@ That was a targeted template: EiffelStudio will propose it whenever the user typ
You can share your code templates using Github You can share your code templates using Github
== Fork the project == == Fork the project ==
Clone your fork, and configure the remotes. [https://github.com/EiffelSoftware/EiffelStudio https://github.com/EiffelSoftware/EiffelStudio ] Clone your fork, and configure the remotes.Eiffel Studio github repository at: [https://github.com/EiffelSoftware/EiffelStudio https://github.com/EiffelSoftware/EiffelStudio ]
# Clone your fork of the repo into the current directory: <code>git clone https://github.com/<your-username>/<repo-name></code> # Clone your fork of the repo into the current directory: <code>git clone https://github.com/<your-username>/<repo-name></code>
# Navigate to the newly cloned directory: <code>cd <repo-name></code> # Navigate to the newly cloned directory: <code>cd <repo-name></code>
@@ -123,7 +123,7 @@ git pull upstream <dev-branch>
== New Branch == == New Branch ==
Create a new topic branch (off the main project development branch) to contain your new code template Create a new topic branch (off the main project development branch) to contain your new code template
<code>git checkout -b <topic-branch-name></code> <code>git checkout -b <topic-branch-name></code>
Commit your changes in logical chunks. Before to commit double check Tim Pope's A Note About Git Commit Messages (http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). Commit your changes in logical chunks. Before to commit double check [http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html Tim Pope's A Note About Git Commit Messages]
Use Git's interactive rebase feature to tidy up your commits before making them public. Use Git's interactive rebase feature to tidy up your commits before making them public.
Locally merge (or rebase) the upstream development branch into your topic branch: Locally merge (or rebase) the upstream development branch into your topic branch: