From 8f084e54acb53a5e9182fa001e42b7c40293a764 Mon Sep 17 00:00:00 2001 From: eiffel-org Date: Wed, 23 Nov 2016 18:35:56 +0000 Subject: [PATCH] Update wikipage Code Templates. (Signed-off-by:javier). git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1695 abb3cda0-5349-4a8f-a601-0c33ac3a8c38 --- .../eiffelstudio-editor/Code-Templates.wiki | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki b/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki index 1e82a466..372d4051 100644 --- a/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki +++ b/documentation/trunk/eiffelstudio/eiffelstudio-reference/eiffelstudio-editor/Code-Templates.wiki @@ -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 == 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: git clone https://github.com// # Navigate to the newly cloned directory: cd @@ -123,7 +123,7 @@ git pull upstream == New Branch == Create a new topic branch (off the main project development branch) to contain your new code template git checkout -b -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. Locally merge (or rebase) the upstream development branch into your topic branch: