Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
contribute:dev:git:userrepos [2014/03/06 09:12] – nick | contribute:dev:git:userrepos [2019/09/08 09:45] – [Repository maintenance] kevinbowen | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
- | Contributors now have the possibility | + | Contributors now have the ability |
users/ | users/ | ||
- | This is useful when you have no permission to commit upstream directly or you want to work on some code privately without bothering other. Compared to upstream repositories, | + | This is useful when you do not have permission to commit upstream directly or you want to work on some code privately without bothering other developers. Compared to upstream repositories, |
* You can create any branch name and delete them | * You can create any branch name and delete them | ||
- | * Possible | + | * It is possible |
* You can decide which other users have write access to your repository as well, see below | * You can decide which other users have write access to your repository as well, see below | ||
- | * No notification emails are send to the xfce4-commits mailing list | + | * No notification emails are sent to the xfce4-commits mailing list |
- | So also for developers with up-stream access rights, it is always advised to work on large patches in a user repository first. | + | As with developers with up-stream access rights, it is always advised to work on large patches in a user repository first. |
+ | |||
+ | < | ||
===== Push to a private repository ===== | ===== Push to a private repository ===== | ||
- | Most often you will continue from the upstream repository and then push your changes on top of that to your user repo branch. If so follow the steps below: | + | Most often you will continue from the upstream repository and then push your changes on top of that to your user repo branch. If so, follow the steps below: |
<file bash> | <file bash> | ||
Line 28: | Line 30: | ||
# create a new branch | # create a new branch | ||
# note we give the local branch name a different name so you can see to which remote it points | # note we give the local branch name a different name so you can see to which remote it points | ||
- | git checkout -b private-bug-1234 --track private/bug-1234 | + | git checkout -b private-bug-1234 |
# improve the code and make commits | # improve the code and make commits | ||
Line 34: | Line 36: | ||
# push you changes | # push you changes | ||
# the first time you do this, the server will create the repository if needed | # the first time you do this, the server will create the repository if needed | ||
- | git push | + | git push -u private private-bug-1234 |
</ | </ | ||
+ | |||
+ | Then, wait for a few minutes for the git repo to be available on https:// | ||
===== Repository maintenance ===== | ===== Repository maintenance ===== | ||
- | There are a couple of commands for gitolite | + | There are a couple of commands for [[https:// |
+ | |||
+ | |||
+ | ==== Fast forward ==== | ||
+ | |||
+ | Note that you can't use non fast-forward pushes. However in user branches, you can remove, then repush your work. | ||
+ | |||
+ | <file bash> | ||
+ | git push user :branch ; git push user branch | ||
+ | </ | ||
==== Give other users write access ==== | ==== Give other users write access ==== | ||
- | By default you are the only user with write access to the repository. To allow other to push changes as well (they can only push forward commits, and have no rights to create and delete), use this command: | + | By default, you are the only user with write access to the repository. To allow others |
- | <file bash>ssh git@git.xfce.org perms users/ | + | <file bash>ssh git@git.xfce.org perms users/ |
- | The same command as above but with the minus-sign | + | To revoke permissions, |
+ | <file bash>ssh git@git.xfce.org perms users/ | ||
For more options, like listing permissions, | For more options, like listing permissions, | ||
<file bash>ssh git@git.xfce.org perms -h</ | <file bash>ssh git@git.xfce.org perms -h</ | ||
+ | |||
+ | ==== Deleting your user repositories ==== | ||
+ | |||
+ | If you finished work in your user repository and it has been merged into the mainline, you can delete it from the server. Only the creator of the repo can delete it. Deleting is not done by removing all of the branches through '' | ||
+ | |||
+ | |||
+ | <file bash>ssh git@git.xfce.org D -h</ | ||
+ | |||
+ | For example, you can delete the xfwm4 repository we created earlier as follows: | ||
+ | |||
+ | <file bash># unlock the repository to allow deletion | ||
+ | ssh git@git.xfce.org D unlock users/ | ||
+ | |||
+ | # remove the repository from the server | ||
+ | ssh git@git.xfce.org D rm users/ | ||
+ | </ |