-
Notifications
You must be signed in to change notification settings - Fork 39
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
Distribute Robo commands via Packagist [4h] #568
Comments
^^ @amitaibu Worth to try? |
https://chat.openai.com/share/0ba365e8-13dc-4282-9f02-ac7b591b4034 The local RoboFile would look like something like this:
So we would be able to override things for project-specifics. |
Sounds like a great idea. And a great demo for AI assistance 👌 |
AronNovak
changed the title
Distribute Robo commands via Packagist
Distribute Robo commands via Packagist [4h]
Sep 21, 2023
We have all the packages here: https://packagist.org/packages/gizra/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have some client projects where we compose custom code via composer. It has a number of benefits:
We have this thing that we copy-paste Robo commands from Drupal Starter. From some projects, we diverge so much from the origin that we can't do better. But many projects are really really similar to Starter when it comes to tooling, but yet, each one is a little bit different.
If we'd try to publish a composer package that holds our commands, we would be able to upgrade (let's say to have the latest release notes generation or fixes in the deploy flow) via composer, just like as we upgrade Drupal core.
The text was updated successfully, but these errors were encountered: