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
fc9a03ff
Verified
Commit
fc9a03ff
authored
1 year ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
howto/git: fix headings
All the howtos were under the "Commit hooks" docs, weird.
parent
90eb5691
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
howto/git.md
+6
-6
6 additions, 6 deletions
howto/git.md
with
6 additions
and
6 deletions
howto/git.md
+
6
−
6
View file @
fc9a03ff
...
...
@@ -240,13 +240,13 @@ Changes to most repositories are reported to:
*
Some repositories have a dedicated mailing list for commits at https://lists.torproject.org
##
#
How to migrate a Git repository from legacy to GitLab?
## How to migrate a Git repository from legacy to GitLab?
Moving a repository from Gitolite to GitLab proceeds in two parts. One
part can be done by any user with access to GitLab. The second part
needs to be done by TPA.
###
#
User part: importing the repository into GitLab
### User part: importing the repository into GitLab
This is the part you need to do as a user to move to GitLab:
...
...
@@ -306,7 +306,7 @@ please make that explicit in the issue and use the proper verb tenses.
See
[
issue tpo/tpa/team#41181
](
https://gitlab.torproject.org/tpo/tpa/team/-/issues/41181
)
for an example issue as well,
although that one doesn't use the proper verb tenses
###
#
TPA part: lock down the repository and add redirections
### TPA part: lock down the repository and add redirections
This part handles the server side of things. It will install a
`pre-receive`
hook in the Git repository to forbid pushes,
...
...
@@ -341,7 +341,7 @@ It assumes the repository has already been migrated.
repo debian/torproject-keyring
##
#
Mirroring a gitolite repository to GitLab
## Mirroring a gitolite repository to GitLab
This procedure is DEPRECATED. Instead, consider
[
migrating the
repository to GitLab permanently
](
#how-to-migrate-a-git-repository-from-legacy-to-gitlab
)
or simply destroying the
...
...
@@ -383,7 +383,7 @@ This procedure is kept for historical purposes only.
In that example, the `translation.git` repository will push to the
`tpo/web/translation` mirror.
##
#
Archiving a repository
## Archiving a repository
IMPORTANT: this procedure is DEPRECATED. Repositories archived on
Gitolite
*still*
will be migrated to GitLab, follow the
[
migration
...
...
@@ -435,7 +435,7 @@ The only downside with that approach is that a git clone will not warn
about the project redirection, but I am not sure there's a way to fix
that.
##
#
GitHub and GitLab Mirrors implementation details
## GitHub and GitLab Mirrors implementation details
Some repositories are mirrored to https://github.com/torproject
organization and to the https://gitlab.torproject.org/ server, through
...
...
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