User Tools
devel:git-commit-guidelines
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
devel:git-commit-guidelines [2018/10/24 22:30] henningw add explanations about github forking |
devel:git-commit-guidelines [2018/10/24 22:33] (current) henningw [Read-Only Cloning of GIT Repository] |
||
|---|---|---|---|
| Line 47: | Line 47: | ||
| 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: | 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: | ||
| - | [[hhttps:// | + | [[https:// |
| [[https:// | [[https:// | ||
| ===== 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, | + | **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 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.1540413041.txt.gz · Last modified: 2018/10/24 22:30 by henningw
Page Tools
