Changes
Page history
mention how fabric could automatically tell GitLab to import projects
authored
Sep 28, 2023
by
anarcat
Hide whitespace changes
Inline
Side-by-side
howto/git.md
View page @
742fad27
...
@@ -319,6 +319,25 @@ are migrating a TPA repository, *do* make sure to first follow the
...
@@ -319,6 +319,25 @@ are migrating a TPA repository, *do* make sure to first follow the
above procedure as the procedure below doesn't do anything to actually
above procedure as the procedure below doesn't do anything to actually
mirror or archive the repository to GitLab (yet).
mirror or archive the repository to GitLab (yet).
> (That said, it *should* be possible to do the following procedure to
> automate this:
>
> 1. clone the repository
>
> git clone https://git.torproject.org/$GITOLITE_PROJECT
>
> 2. push to GitLab ([creating a private project](https://docs.gitlab.com/ee/user/project/#create-a-new-project-with-git-push))
>
> git remote set-url origin https://gitlab.torproject.org/$GITLAB_PROJECT
>
> 3. adjust the project's privacy setting (making it public, most
> likely)
>
> 4. optionally archive the GitLab project
>
> Steps 4 and 5 would require GitLab API access. Alternatively, the
> [create project API has an `import_url` field](https://docs.gitlab.com/ee/api/projects.html#create-project).)
The procedure is this simple two-step process:
The procedure is this simple two-step process:
1.
(optional) triage the ticket with the labels ~Git and ~Gitweb, and
1.
(optional) triage the ticket with the labels ~Git and ~Gitweb, and
...
...
...
...