GitLab | Workflow for contrib projects (#99)

[Christian Mauderer (@c-mauderer)]

Christian Mauderer commented on a discussion: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124694


My experience with a private GitLab instance (community edidtion) is that the URL redirections are valid as long as you don't create a new project with the same URL. But you get a warning during pulls and pushes that you should update your URL.

That's for git projects and some other parts (like users). But it's not true for example for API calls, CODEOWNER files, includes in the CI scripts and similar:

https://docs.gitlab.com/user/project/repository/#repository-path-changes

Beneath that, there is also a potential attack surface: If a top level group is renamed, an attacker could create a new user with that name and take over the namespace with that. Even if it is discovered quickly, it will destroy the old namespace.

-- 
View it on GitLab: https://gitlab.rtems.org/administration/gitlab/-/issues/99#note_124694
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250616/b6fed78f/attachment.htm>