Change Details

When looking at GitLab forges we'd be able to ingest, I came across the Drupal forge. https://git.drupalcode.org/explore It looks like they have two namespaces: - one namespace for the main repository of all maintained projects (/project/) - one namespace for "issue collaboration forks" (/issues/) Afaict, forks in the issues namespace are automatically generated for every ticket in their issue tracker, so that contributors can collaborate on patches. Patches are automatically (?) submitted as merge requests on the main repository. I believe that we could archive this forge, but the issues namespace is noise that would be taken into account through the merge-request refs in the main repositories, and that it would be useful to filter it out on the lister side. In that same vein, on the main gitlab.org instance, there's a bunch of transient repositories generated by the gitlab QA process that could be filtered out. https://gitlab.com/gitlab-qa-sandbox-group-1 ...

When looking at GitLab forges we'd be able to ingest, I came across the Drupal forge. https://git.drupalcode.org/explore It looks like they have two namespaces: - one namespace for the main repository of all maintained projects (/project/) - one namespace for "issue collaboration forks" (/issues/) Afaict, forks in the issues namespace are automatically generated for every ticket in their issue tracker, so that contributors can collaborate on patches. Patches are automatically (?) submitted as merge requests on the main repository. I believe that we could archive this forge, but the issues namespace is noise that would be taken into account through the merge-request refs in the main repositories, and that it would be useful to filter it out on the lister side. In that same vein, on the main gitlab.com instance, there's a bunch of transient repositories generated by the gitlab QA process that could be filtered out. https://gitlab.com/gitlab-qa-sandbox-group-1 ...

When looking at GitLab forges we'd be able to ingest, I came across the Drupal forge. https://git.drupalcode.org/explore It looks like they have two namespaces: - one namespace for the main repository of all maintained projects (/project/) - one namespace for "issue collaboration forks" (/issues/) Afaict, forks in the issues namespace are automatically generated for every ticket in their issue tracker, so that contributors can collaborate on patches. Patches are automatically (?) submitted as merge requests on the main repository. I believe that we could archive this forge, but the issues namespace is noise that would be taken into account through the merge-request refs in the main repositories, and that it would be useful to filter it out on the lister side. In that same vein, on the main gitlab.orgcom instance, there's a bunch of transient repositories generated by the gitlab QA process that could be filtered out. https://gitlab.com/gitlab-qa-sandbox-group-1 ...