tkammer-zz
commented
7 years ago I completely agree. This has been a task that will be done once we finish migrating to infrared 2.0 (it will be a different repo structure).
On Tue, Dec 20, 2016 at 1:05 PM, Sorin Sbarnea notifications@github.com wrote:
In order to improve our user experience, please make InfraRed github repository lowercase instead of using CamelCase. This may seem as a not very important but remember that the repo-name is used as the default folder name when you checkout the code, going to standard way would only help everyone.
In case Github does not allow you to rename it directly from InfraRed to infrared you can use a two-step process: InfraRed -> infrared.temp -> infrared.
This can be done without loosing any data, some URLs may need too be updated but that's small price to pay for improving the user experience.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/rhos-infra/InfraRed/issues/277, or mute the thread https://github.com/notifications/unsubscribe-auth/AC11Ps-Kv_eLkE59gOPpxH6Ipxpr1BDEks5rJ7aUgaJpZM4LRt4I .
-- Tal Kammer Associate manager, automation and infrastructure, Openstack platform. Red Hat Israel Automation group mojo: https://mojo.redhat.com/docs/DOC-1011659
In order to improve our user experience, please make InfraRed github repository lowercase instead of using CamelCase. This may seem as a not very important but remember that the repo-name is used as the default folder name when you checkout the code, going to standard way would only help everyone.
In case Github does not allow you to rename it directly from
InfraRedtoinfraredyou can use a two-step process:InfraRed->infrared.temp->infrared.This can be done without loosing any data, some URLs may need too be updated but that's small price to pay for improving the user experience.