Developers Github Guide - Revision history

Cooperl: /* Protégé software */

2015-09-07T21:22:11Z

Protégé software

Cooperl: /* GitHub access via command-line interface */

2015-09-07T21:21:25Z

GitHub access via command-line interface

Cooperl: /* GitHub access via command-line interface */

2015-09-07T21:20:47Z

GitHub access via command-line interface

Cooperl: /* GitHub access via command-line interface */

2015-09-07T21:19:50Z

GitHub access via command-line interface

Cooperl: /* GitHub access via command-line interface */

2015-09-07T21:19:02Z

GitHub access via command-line interface

Cooperl: /* Plant Ontology: Developers guide to Github access */

2015-09-07T21:18:10Z

Plant Ontology: Developers guide to Github access

Meiera: /* Github access via command-line interface */

2015-09-02T21:28:51Z

Github access via command-line interface

Meiera: /* Get an account from Github administrator */

2015-09-02T21:22:05Z

Get an account from Github administrator

Meiera: /* Github access via unix or linux machines (Mac OS included) */

2015-09-02T21:20:28Z

Github access via unix or linux machines (Mac OS included)

Meiera at 21:19, 2 September 2015

2015-09-02T21:19:43Z

@@ Line 78: / Line 78: @@
 ===Protégé software===
-[http://protege.stanford.edu/ Protégé] is a free, open source ontology editor and knowledge-base framework that is useful if you want to edite ontlogies in RDF(S), OWL, or XML Schema.
+[http://protege.stanford.edu/ Protégé] is a free, open source ontology editor and knowledge-base framework that is useful if you want to edit ontologies in RDF(S), OWL, or XML Schema.
 Protégé is based on Java, is extensible, and provides a plug-and-play environment that makes it a flexible base for rapid prototyping and application development.

@@ Line 52: / Line 52: @@
 <code>git push</code>
-'''It is good practice always to pull a file before revising it.
+'''It is good practice always to pull a file before revising it.'''
 '''
 At any time you can check the status of your local repository vs. the master on Github by typing:
 <code>git status</code>
-There is a helpful [https://help.github.com/articles/good-resources-for-learning-git-and-github/ guide] on Github's help page.
+There is a helpful [https://help.github.com/articles/good-resources-for-learning-git-and-github/ guide] on GitHub's help page.
 If you need help in depositing your files, please contact one of us:
 [mailto:jaiswalp@science.oregonstate.edu?Subject=Plantontology%20SVN%20help Pankaj Jaiswal],[mailto:jaiswalp@science.oregonstate.edu?Subject=Plantontology%20SVN%20help Laurel Cooper], [mailto:jaiswalp@science.oregonstate.edu?Subject=Plantontology%20SVN%20help Justin Elser]

@@ Line 19: / Line 19: @@
 ==GitHub access via command-line interface==
-If you prefer a command line access via a unix or linux machines, try this.
+If you prefer a command line access via on a Mac, unix, or linux machines, try this.
 Set up a directory on your local computer, with a name of your choice (such as 'plant-ontology':

@@ Line 52: / Line 52: @@
 <code>git push</code>
-It is good practice always to pull a file before revising it.
+'''It is good practice always to pull a file before revising it.
+'''
 At any time you can check the status of your local repository vs. the master on Github by typing:

@@ Line 21: / Line 21: @@
 If you prefer a command line access via a unix or linux machines, try this.
-Set up a directory on your home box:
+Set up a directory on your local computer, with a name of your choice (such as 'plant-ontology':
 <code>

@@ Line 1: / Line 1: @@
-=Plant Ontology: Developers guide to Github access=
+=Plant Ontology: Developers guide to GitHub access=
-==Get an account from Github administrator==
+==Get an account from GitHub administrator==
-To be granted developer access to the Github Plant-ontology repository you need to have a Github account and password.  Follow on-screen instructions at https://github.com/
+To be granted developer access to the GitHub Plant-ontology repository you need to have a GitHub account and password.  Follow on-screen instructions at https://github.com/
-To get developer access, please email your Github username to Justin Elser and by mentioning the following:
+To get developer access, please email your GitHub username to Justin Elser and by mentioning the following:
-Request for Github developers account on: Planteome/plant-ontology/ repository
+Request for GitHub developers account on: Planteome/plant-ontology/repository
 Your name:
 Institution:
 Email address:
 Office or lab telephone number:(xxx)-xxx-xxxx
-Github account name:
+GitHub account name:
 If you already have one, do not worry, it will work. Once you have developer status, start with the following set of instructions.  The terminal you use with vary depending on the type of machine from which you will be using.
-==Github access via command-line interface==
+==GitHub access via command-line interface==
 If you prefer a command line access via a unix or linux machines, try this.
@@ Line 24: / Line 24: @@
 <code>
-mkdir ontology
+mkdir plant-ontology
-cd ontology
+cd plant-ontology
 </code>
 Get the files by cloning the repository:
-<code>git clone <nowiki>https://github.com/Planteome/plant-ontology.git</nowiki> </code>
+<code> git clone <nowiki>https://github.com/Planteome/plant-ontology.git</nowiki> </code>
 In order to update an ontology, do this:

@@ Line 37: / Line 37: @@
 <code>git pull</code>
-Make your changes to the ontology files, then
+Make your changes to the ontology files, then stage your modified file to your local repository before committing it.
 <code>git add name_of_file_that_has_been_changed.obo</code>
 To commit your changes:

← Older revision		Revision as of 21:22, 2 September 2015
Line 15:		Line 15:


−	If you already have one, do not worry, it will work. Once you have developer status, start with ~~one of~~ the following ~~sets~~ of instructions, depending on the type of machine from which you will be ~~accessing the SVN repository~~.	+	If you already have one, do not worry, it will work. Once you have developer status, start with the following set of instructions. The terminal you use with vary depending on the type of machine from which you will be using.

	==Github access via command-line interface==		==Github access via command-line interface==

@@ Line 17: / Line 17: @@
 If you already have one, do not worry, it will work. Once you have developer status, start with one of the following sets of instructions, depending on the type of machine from which you will be accessing the SVN repository.
-==Github access via unix or linux machines (Mac OS included)==
+==Github access via command-line interface==
 If you prefer a command line access via a unix or linux machines, try this.
@@ Line 63: / Line 63: @@
 If you need help in depositing your files, please contact one of us:
 [mailto:jaiswalp@science.oregonstate.edu?Subject=Plantontology%20SVN%20help Pankaj Jaiswal],[mailto:jaiswalp@science.oregonstate.edu?Subject=Plantontology%20SVN%20help Laurel Cooper], [mailto:jaiswalp@science.oregonstate.edu?Subject=Plantontology%20SVN%20help Justin Elser]
 ==Ontology editing software:==

← Older revision		Revision as of 21:19, 2 September 2015
Line 55:		Line 55:

	It is good practice always to pull a file before revising it.		It is good practice always to pull a file before revising it.
		+
		+	At any time you can check the status of your local repository vs. the master on Github by typing:
		+
		+	<code>git status</code>

	There is a helpful [https://help.github.com/articles/good-resources-for-learning-git-and-github/ guide] on Github's help page.		There is a helpful [https://help.github.com/articles/good-resources-for-learning-git-and-github/ guide] on Github's help page.