Plugins and Themes mirrors

[viktorix]

In order to prevent plugins/themes from disappearing if a developer decides to delete their repos, we need to have a backup. We started the plugins mirror. I'm trying to see if I can get access to it. If not, we'll start with a new org.

Should we have one org for plugins/themes, or have a separate org for plugins mirror and themes mirror?

We need to figure out a way to automate the process, so the directory can trigger creation and updates to the mirrors.

[xxsimoxx]

We just need the default branch, right?
If we have gh installed somewhere (with access rights to the org) it's not so much difficult to write a script to do so.
Just for memory:

gh repo fork KTS915/Object-Relationships --remote=true --clone=false --fork-name plugin_KTS915_Object-Relationships --org "ClassicPressBackup"
gh repo sync ClassicPressBackup/plugin_Object-Relationships

[viktorix]

@xxsimoxx do you think we need 2 separate organizations, one for theme and one for plugins? Or one will do? I'm not seeing a specific reason for having separate orgs.

We just need the default branch, right?

I'm not sure exactly what we need. But I assume it needs to include releases and zip files, so it can be a drop-in replacement when the original repo is deleted. I just don't know what's possible. @striebwj said he might be able to help with automation here.

[xxsimoxx]

We need two orgs just if we have to keep the original plugin name and we can have a plugin and a theme with the same slug.
If we can rename repo-x to plugin_repo-x we just need one org.

[viktorix]

OK, that makes sense. I didn't think about identical slugs.