vyos/vyos-documentation
1
0
Fork 0
mirror of https://github.com/vyos/vyos-documentation.git synced 2025-10-26 08:41:46 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #351 from noah-de/forking-workflow-revisions

Browse Source 
Forking Workflow: revisions to the forking workflow instructions
This commit is contained in:
Christian Poessinger 2020-10-23 13:20:45 +02:00 committed by GitHub
commit e8cfda5cda
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/contributing/documentation.rst
View File

@ -35,12 +35,12 @@ access to the official codebase.
* Fork this project on GitHub https://github.com/vyos/vyos-documentation/fork * Fork this project on GitHub https://github.com/vyos/vyos-documentation/fork
* Clone fork to local machine * Clone fork to local machine, then change to that directory``$ cd vyos-documentation``
* Change to your new local directory ``$ cd vyos-documentation`` * Install the requirements ``$ pip install -r requirements.txt`` (or something similar)
* Create new branch for your work, use a descriptive name of your work: * Create new branch for your work, use a descriptive name of your work:
``$ git checkout -b fix-vxlan-typo`` ``$ git checkout -b <branch-name>``
* Make all your changes - please keep our commit rules in mind * Make all your changes - please keep our commit rules in mind
(:ref:`prepare_commit`). This mainly applies to proper commit messages (:ref:`prepare_commit`). This mainly applies to proper commit messages
@ -61,11 +61,12 @@ access to the official codebase.
unstaged files ``$ git add .``. All files added to the Git index will be part unstaged files ``$ git add .``. All files added to the Git index will be part
of you following Git commit. of you following Git commit.
* Commit your changes ``$ git commit -v`` - your configured editor will now ne * Commit your changes with the message, ``$ git commit -m "<commit message>"``
launched where you can type in a commit message. Again please make yourself or use ``$ git commit -v`` to have your configured editor launched. You can
comfortable with out rules (:ref:`prepare_commit`). type in a commit message. Again please make yourself comfortable with out
rules (:ref:`prepare_commit`).
* Push your commits to your GitHub project: ``$ git push -u origin foo-branch`` * Push commits to your GitHub project: ``$ git push -u origin <branch-name>``
* Submit pull-request. In GitHub visit the main repository and you should * Submit pull-request. In GitHub visit the main repository and you should
see a banner suggesting to make a pull request. Fill out the form and see a banner suggesting to make a pull request. Fill out the form and