-
-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repository name #107
Comments
👍 |
1 similar comment
👍 |
Agreed. This also matches our naming schema in relation to Odoo modules. Delivery is one & carrier is not, so delivery should be first. 👍 |
👍 Where to rename it: OCA/maintainer-tools
Most of this can be done later as github does the alias but in the long term we want to rename it everywhere. Am I missing something? I guess that coverall and travis will follow the change without issue. |
Good recompilation. I don't miss anything |
ok then, who push the button ? |
I don't have access to those settings I think it's someone of @OCA/board noone else has admin rights on repositories |
By the way robots are starting to do a takeover of the world a member of the board is @oca-transbot 😁 |
Uhm, PSC people should have also access I think... I'll do it anyway. |
Renamed! |
Please perform the rest of the list, @yvaucher |
Add the 'waiting' state into the domain list. As moves on this state …
This branch name is carrier-delivery and modules inside are [base_]delivery_carrier_blabla
It's error prone. Nobody can remember what is the real name.
I suggest to rename carrier-delivery repo by delivery-carrier.
As we had could see when switch from lp: to github:, github manage really well alias repositories.
Then there'll no impact to production environment.
Please thanks to vote.
ping @yvaucher @guewen
The text was updated successfully, but these errors were encountered: