Skip to content

Commit 350a3ec

Browse files
authored
changed list numbering
after introducing the location of the csv file, I'm wondering if it needs to be re-introduced in the list. Reviewers can reject this change if it's unnecessary
1 parent 440795a commit 350a3ec

1 file changed

Lines changed: 5 additions & 6 deletions

File tree

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,10 @@
11
## Instructions for Registering new IRIs in CCO
22

3-
Before creating a pull request containing a new CCO term, developers must register the new IRIs in the csv file maintained exclusively in the [contributing documentation section] (https://github.com/CommonCoreOntology/CommonCoreOntologies/tree/iri-registry-branch/documentation/contributing) on this separate [branch](https://github.com/CommonCoreOntology/CommonCoreOntologies/tree/iri-registry-branch/).
3+
Before creating a pull request containing a new CCO term, developers must register the new IRIs in the csv file maintained exclusively in the [contributing documentation section](https://github.com/CommonCoreOntology/CommonCoreOntologies/tree/iri-registry-branch/documentation/contributing) on this separate [branch](https://github.com/CommonCoreOntology/CommonCoreOntologies/tree/iri-registry-branch/).
44

55
To do so:
66

7-
1. Navigate to this [directory](https://github.com/CommonCoreOntology/CommonCoreOntologies/tree/iri-registry-branch/documentation/contributing) on the IRI Registry branch.
8-
2. Open the file `iri-registry.csv` located there and navigate to the bottom row of the file.
9-
3. In the next empty row, add the new IRI(s) as an increment from the last one. Also add your name, the date, and the associated issue number(s).
10-
4. Commit your changes directly to the IRI Registry Branch and push to origin.
11-
6. Now you can open a new branch off of `develop` to execute your work using the IRIs that you have registered.
7+
1. Open the file `iri-registry.csv` located in that directory and navigate to the bottom row of the file.
8+
2. In the next empty row, add the new IRI(s) as an increment from the last one. Also add your name, the date, and the associated issue number(s).
9+
3. Commit your changes directly to the IRI Registry Branch and push to origin.
10+
4. Now you can open a new branch off of `develop` to execute your work using the IRIs that you have registered.

0 commit comments

Comments
 (0)