Clean-up our Praqma repo we forked from about configuration-as-code-plugin HOT 6 CLOSED

I don't think there is anything we need to keep from Praqma repo, feel free to remove

from configuration-as-code-plugin.

We also had one contribution to our Praqma repo... so users might also be confused.

Which is one of the reasons we recommend that people delete their origin repo after we fork their plugin -- the confusion is annoying. As is the limitations GH search imposes on forks.

GitHub support can, on request, revert the fork relationship between repos, and make the jenkinsci one the canonical one.

from configuration-as-code-plugin.

@ewelinawilkosz we have anything we want to keep in our Praqma repo or should we just delete it?

Deleting it seems to be the best solution, and it will then break the fork as I understand. Only problem is I can't according to GH help be sure which fork becomes the new master: https://help.github.com/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility/#deleting-a-public-repository

So I'll probably write to GH support anyway to get them to do it.

from configuration-as-code-plugin.

Yep -- may be one of the personal forks.

from configuration-as-code-plugin.

Cleaned up our repo issues, and are ready to delete when GH support answers back they break the fork for us to ensure the jenkinsci becomes the new master

from configuration-as-code-plugin.

@ewelinawilkosz @ndeloof the fork relation back to the Praqma repo is now removed by Github support - they did it only 12 minutes after I asked yesterday ;-)

So this means I'll kill our Praqma version of this repo and this is now our new "master".

from configuration-as-code-plugin.