developer/new-developers/submitting-your-first-patch: cleanup
linkify Git SSH Change-Id: Iaa766a20a88a3a026db4d8abdd6cbb723a311860
This commit is contained in:
parent
417d82ed74
commit
8b9689bee4
|
@ -1,33 +1,34 @@
|
||||||
Submitting your first patch
|
# Submitting your first patch
|
||||||
===========================
|
|
||||||
|
|
||||||
## Setting up git and ssh
|
|
||||||
|
|
||||||
(**to work smoothly with Gerrit.**)
|
|
||||||
|
|
||||||
|
|
||||||
first see:
|
## Setting up Git and SSH
|
||||||
|
|
||||||
|
(**To work smoothly with Gerrit.**)
|
||||||
|
|
||||||
|
|
||||||
|
First see:
|
||||||
|
|
||||||
* [Creating a gerrit review](working-with-gerrit)
|
* [Creating a gerrit review](working-with-gerrit)
|
||||||
|
|
||||||
|
|
||||||
### SSH setup
|
### SSH setup
|
||||||
|
|
||||||
https://review.jami.net/Documentation/user-upload.html#ssh
|
<https://review.jami.net/Documentation/user-upload.html#ssh>
|
||||||
|
|
||||||
1. Generate a personal dedicated public/private key set.
|
1. Generate a personal dedicated public/private key set.
|
||||||
```bash
|
```bash
|
||||||
ssh-keygen -f ~/.ssh/jami_gerrit_review`
|
ssh-keygen -f ~/.ssh/jami_gerrit_review`
|
||||||
```
|
```
|
||||||
|
|
||||||
Your identification has been saved in `jami_gerrit_review`. Your public key has been saved in `jami_gerrit_review.pub.`
|
Your identification has been saved in `jami_gerrit_review`.
|
||||||
|
Your public key has been saved in `jami_gerrit_review.pub`.
|
||||||
|
|
||||||
|
2. Tell Gerrit your public key
|
||||||
|
1. Login to [Gerrit](https://review.jami.net) via your GitLab account (Sign-in → OAuth GitLab)
|
||||||
|
2. Follow the SSH key instructions found from (your) user options [settings](https://review.jami.net/settings/)
|
||||||
|
|
||||||
2. Tell gerrit your public key
|
3. Set up your local SSH (via `ssh-add` or in `~/.ssh/config`)
|
||||||
1. Login to [gerrit](https://review.jami.net) via your Gitlab account (Sign-in=>OAuth Gitlab)
|
4. Test all of the above (SSH on the service or just try to clone a repo on Gerrit via SSH)
|
||||||
2. Follow the ssh key instructions found from (your) user options [settings](https://review.jami.net/settings/)
|
|
||||||
|
|
||||||
3. Set up your local ssh (via `ssh-add` or in `~/.ssh/config`)
|
|
||||||
4. Test all of the above (ssh on the service or just try to clone a repo on gerrit via ssh)
|
|
||||||
|
|
||||||
|
|
||||||
### Your Repository
|
### Your Repository
|
||||||
|
@ -41,10 +42,8 @@ aka: commit-msg hook script
|
||||||
|
|
||||||
A shell script, to be installed to .git/hooks/commit-msg.
|
A shell script, to be installed to .git/hooks/commit-msg.
|
||||||
|
|
||||||
|
|
||||||
The script creates a unique Change_Id:hash for each commit made from your repository.
|
The script creates a unique Change_Id:hash for each commit made from your repository.
|
||||||
|
|
||||||
|
|
||||||
- The first time you attempt a _push_ to review `git push origin HEAD:refs/for/master`,
|
- The first time you attempt a _push_ to review `git push origin HEAD:refs/for/master`,
|
||||||
gerrit will notice a lack of Change-Id.
|
gerrit will notice a lack of Change-Id.
|
||||||
|
|
||||||
|
@ -52,7 +51,6 @@ The script creates a unique Change_Id:hash for each commit made from your reposi
|
||||||
Use *that* to download a copy of .git/hooks/commit-msg.
|
Use *that* to download a copy of .git/hooks/commit-msg.
|
||||||
|
|
||||||
|
|
||||||
References
|
## References
|
||||||
----------
|
|
||||||
|
|
||||||
+ [Some Gritty Details](https://review.jami.net/Documentation/user-upload.html#_gritty_details)
|
+ [Some Gritty Details](https://review.jami.net/Documentation/user-upload.html#_gritty_details)
|
||||||
|
|
Loading…
Reference in New Issue