On Tue, Feb 5, 2019 at 12:49 PM Barak Korren <bkorren@redhat.com> wrote:
On Tue, 5 Feb 2019 at 12:59, Sandro Bonazzola <sbonazzo@redhat.com> wrote:Il giorno mar 5 feb 2019 alle ore 11:54 Tomáš Golembiovský <tgolembi@redhat.com> ha scritto:Hi,
I would like to rename the GitHub repo ovirt-ansible-v2v-conversion-host
to v2v-conversion-host. Is there a list of things I should do before
or after the operation? Will the automation still work?
Letting infra to answer about this.Before you rename - you need to change the project name in the YAML in the 'jenkins' repo so that you'll get jobs that listen on the new name.Adding Ondra and Martin, didn't we have a rule for repository naming related to ansible roles?
We try to stick with the convention for oVirt roles, but as Tomas explained v2v-conversion is no more oVirt only role, it's being used by oVirt, CFME and newly also CNV, so it makes sense to rename (although renaming adds a lot of burden to do package upgrade properly)
_______________________________________________--
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/JOLIWOBZNIZGR77TAOOMAODEZVXIMXPH/
--Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
