Permission-wise I can do both of it, I'm just vaguely wondering if there's anything involved I'm not aware of that could break.

For unknown reasons https://gitlab.wikimedia.org/toolforge-repos/povoconta/-/commits/master exists

striker_admin@m5-master.eqiad.wmnet(striker)> select * from tools_gitlabrepo where name = 'povoconta'\G
*************************** 1. row ***************************
           id: 216
         tool: povoconta
         name: povoconta
      repo_id: 673
 created_date: 2022-09-07 22:23:14.371532
created_by_id: 112
1 row in set (0.002 sec)

striker_admin@m5-master.eqiad.wmnet(striker)> select ldapname, shellname, sulname from labsauth_labsuser where id=112;
+-----------+-----------+-----------+
| ldapname  | shellname | sulname   |
+-----------+-----------+-----------+
| Ederporto | ederporto | Ederporto |
+-----------+-----------+-----------+
1 row in set (0.001 sec)

@Ederporto used https://toolsadmin.wikimedia.org to create a Diffusion repository on 2022-09-07. That Diffusion repo was then migrated to https://gitlab.wikimedia.org as part of T315706: Migrate existing Striker created Diffusion repos to GitLab.

In T348325#9231111, @Aklapper wrote:

Permission-wise I can do both of it, I'm just vaguely wondering if there's anything involved I'm not aware of that could break.

It will break rendering of https://toolsadmin.wikimedia.org/tools/id/povoconta/repos/id/673 which is linked from https://toolsadmin.wikimedia.org/tools/id/povoconta. That can be fixed by manually deleting the tools_gitlabrepo row shown in T348325#9436799. Today Striker does not have a delete function for either GitHub repos or Phabricator projects it has created to make cleaning up after this sort of change of mind by tool maintainers easier.

I deleted the out-of-sync Diffusion repo at https://phabricator.wikimedia.org/source/tool-povoconta/ ; untagging Diffusion-Repository-Administrators