Fixed references in CONTRIBUTING.md

Signed-off-by: Christian Herber <christian.herber@oss.nxp.com>
This commit is contained in:
Christian Herber 2023-01-04 13:45:23 +01:00
parent 2d7bb4aea5
commit 5cd0623715

View file

@ -3,9 +3,9 @@ Contributors are encouraged to be a [member](https://www.openhwgroup.org/members
OpenHW Group. New members are always welcome.
## Getting Started
The [OpenHW Work Flow](https://github.com/openhwgroup/core-v-docs/blob/master/verif/Common/OpenHWGroup_WorkFlow.pdf) document
The [OpenHW Work Flow](https://github.com/openhwgroup/programs/blob/5fa810bf16d25cf32c7eca58be084975bec38f96/TGs/verification-task-group/documents/presentations/OpenHWGroup_WorkFlow.pdf) document
is required reading. You will find information about the implementation and usage of the CORE-V verification environments
in the [Verification Strategy](https://github.com/openhwgroup/core-v-docs/blob/master/verif/Common/OpenHWGroup_CORE-V_Verif_Strategy.pdf).
in the [Verification Strategy](https://docs.openhwgroup.org/projects/core-v-verif/en/latest/index.html).
## The Mechanics
1. From GitHub: [fork](https://help.github.com/articles/fork-a-repo/) the [cve2](https://github.com/openhwgroup/cve2) repository
@ -13,6 +13,6 @@ in the [Verification Strategy](https://github.com/openhwgroup/core-v-docs/blob/m
3. Create your feature branch: `git checkout -b <my_branch>.`<br> Please uniquify your branch name. See the [Git Cheats](https://github.com/openhwgroup/core-v-verif/blob/master/GitCheats.md)
for a useful nominclature.
4. Make your edits...
5. Commit your changes: `git commit -m 'Add some feature' -s`<br>...take note of that **-s**, it's important!
5. Commit your changes: `git commit -m 'Add some feature' -s`<br>; `-s` or `--sign-off` is engouraged, but not required.
6. Push feature branch: `git push origin <my_branch>`
7. From GitHub: submit a pull request