Contributors now have the possibility to create user repositories. This allows all developers with git permissions to create their own repository with the following wildcard:
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, user repositories have more permissions (for the creator):
- You can create any branch name and delete them
- Possible to rewind push / loose commits (see the
- 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
So also for 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
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:
# clone the upstream repository git clone git://git.xfce.org/xfce/xfwm4 # add a new remote repository with the name 'private' git remote add private ssh://firstname.lastname@example.org/users/$user/xfwm4 # create a new branch # 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 # improve the code and make commits # push you changes # the first time you do this, the server will create the repository if needed git push -u private private-bug-1234
Then wait for a few minutes for the git repo to be available on https://git.xfce.org interface.
There are a couple of commands for gitolite to maintain your private repository.
Note that you can't use non fast forward pushes. However, in user branches, you can remove then repush your work.
git push user :branch ; git push user branch
Give other users write access
By default you are the only user with write access to the repository. To allow others to push changes as well (they can only push forward commits, and have no rights to create and delete), use this command:
ssh email@example.com perms users/$user/$repo + WRITERS $otheruser
The same command as above but with the minus-sign can be used to revoke the permission.
For more options, like listing permissions, see the usage help of the
ssh firstname.lastname@example.org perms -h
Delete your user repositories
If you finished work in your user repository and it's merged in mainline, you can delete it from the server. Only the creator of the repo can delete it. Deleting is not by removing all the branches though
git push, but with ssh commands on the server. For help on this command run the following in a terminal.
ssh email@example.com D -h
As an example you can delete the xfwm4 repository we created earlier as follows:
# unlock the repository to allow deletion ssh firstname.lastname@example.org D unlock users/$user/xfwm4 # remove the repository from the server ssh email@example.com D rm users/$user/xfwm4