Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
TPA
Wiki Replica
Commits
e98f9575
Commit
e98f9575
authored
4 years ago
by
Iain R. Learmonth
Browse files
Options
Downloads
Patches
Plain Diff
git explain gitolite config
parent
1d815e0c
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
git.mdwn
+61
-4
61 additions, 4 deletions
git.mdwn
with
61 additions
and
4 deletions
git.mdwn
+
61
−
4
View file @
e98f9575
...
...
@@ -64,18 +64,75 @@ repo metrics-cloud
metrics-cloud "The Tor Project" = "Configurations for Tor Metrics cloud orchestration"
```
The last line of this file is what is used to provide configuration to gitweb.
In this case, the permissions are delegated to a group and not an individual
user. Groups are defined at the top of the file, again in alphabetical order:
Deconstructing this:
```
@metrics-cloud = karsten irl
repo metrics-cloud
```
Starts a repository block.
```
RW = @metrics-cloud
```
Allows non-destructive read/write but not branch/tag deletion or
non-fast-forward pushes. Alternatives would include "R" for read-only, or
"RW+" to allow for destructive actions. We only allow destructive actions for
user's personal repositories.
In this case, the permissions are delegated to a group (starting with @) and
not an individual user.
```
config hooks.email-enabled = true
config hooks.mailinglist = tor-commits@lists.torproject.org
```
This enables the email hook to send one email per commit to the commits list.
For all top-level repositories, the mailing list should be
tor-commits@lists.torproject.org.
```
config hooks.irc-enabled = true
config hooks.ircproject = or
```
This enables the IRC hook to send one message per commit to an IRC channel. If
the project is set to "or" the messages will be sent to #tor-bots.
```
config hooks.githuburl = torproject/metrics-cloud
config hooks.gitlaburl = torproject/metrics/metrics-cloud
```
These enable pushing a mirror to external services. The external service will
have to be configured to accept these pushes, and we should avoid adding
mirror URLs where things aren't configured yet so we don't trigger any IPS or
abuse detection system by making loads of bad push attempts.
```
metrics-cloud "The Tor Project" = "Configurations for Tor Metrics cloud orchestration"
```
The last line of this file is what is used to provide configuration to gitweb.
Starting with the path, then the owner, then the short description.
Upon push, the new repository will be created. It may take some minutes to
appear on the gitweb. Do not fear, the old list that did not yet include the
new repository has just been cached.
Push takes ages. Don't Ctrl-C it or you can end up in an inconsistent state.
Just let it run. A future git team member might work on backgrounding the
sync task.
Groups are defined at the top of the file, again in alphabetical order
(not part of the repository block):
```
@metrics-cloud = karsten irl
```
### Adding developers to a repository
If you want access to an existing repository please have somebody who already
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment