User Tools

Site Tools


devel:git-commit-guidelines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
devel:git-commit-guidelines [2018/03/12 13:03]
miconda [Generic Guidelines]
devel:git-commit-guidelines [2018/10/24 22:33]
henningw [Working with Github forks of a GIT Repository]
Line 42: Line 42:
  
 The clone is tracking automatically the remote **master** branch (the development version). The clone is tracking automatically the remote **master** branch (the development version).
 +
 +===== Working with Github forks of a GIT Repository =====
 +
 +If you don't have developer write access, you can fork the Kamailio repository. Then you checkout the forked repository to your local disk and do the changes. Commit the changes to your repository and create a pull request to integrate your changes into the Kamailio repository back. Have a look e.g. to this documentation:
 +
 +[[https://help.github.com/articles/fork-a-repo/|Github help - forking]]
 +
 +[[https://help.github.com/articles/about-pull-requests/|Github help - pull request]]
  
 ===== Read-Only Cloning of GIT Repository ===== ===== Read-Only Cloning of GIT Repository =====
 +
 +**Working with a fork of the Kamailio repository and then submitting a pull request is nowadays the preferred way to integrate your contributions, if you don't have write permissions to the Kamailio repository. Please see above.**
  
 If you don't have developer write access, you can clone read-only the repository with: If you don't have developer write access, you can clone read-only the repository with:
devel/git-commit-guidelines.txt ยท Last modified: 2018/10/24 22:33 by henningw