thinkshout / robo-drupal
Robo Tasks for Drupal projects
Installs: 69 203
Dependents: 2
Suggesters: 0
Security: 0
Stars: 7
Watchers: 3
Forks: 0
Open Issues: 7
Requires
- consolidation/annotated-command: <=4.5.6
- consolidation/robo: ^3.0
- drupal/config_split: ^2.0
- drush/drush: ^9.6|^10.0|^11.1
- genesis/behat-fail-aid: ^3.7
- vlucas/phpdotenv: >=5.0
- dev-production
- 4.x-dev
- v3.4.1
- v3.4.0
- v3.3.0
- v3.2.0
- v3.2.0-rc1
- v3.1.1
- v3.1.0
- v3.0.2
- v3.0.1
- v3.0.0
- v2.0.2
- v2.0.1
- v2.0.0
- 2.0-rc1
- 1.0
- dev-php81
- dev-issue-annotated-command
- dev-robo4
- dev-behat
- dev-drush11
- dev-issue-73
- dev-dotenv_compatibility
- dev-dotenvupdate
- dev-faster-config-pull
- dev-master
- dev-backup_messaging
- dev-pantheon-files-protection
- dev-60-config-split-naming
- dev-drush
- dev-auto-update
- dev-51-no-more-entup
- dev-pantheon-install-2
- dev-pantheon-install-parity
- dev-issue-40-multidevs-fail
- dev-16-create-db
- dev-create-function-apply-update
- dev-pull-config-backup-date
- dev-circle-updates
- dev-small-circle-docker-fixes
- dev-43-robo-drupal-documentation
- dev-2-replace-dash-with-underscore-in-db-name
- dev-upgrade-drush-9.6
- dev-sql-drop-syntax
- dev-updated-dependencies
- dev-issue-17-sql-sync-terminus-wget
- dev-18_existing_config
- dev-vr-build-hotfix
- dev-updated-robo
- dev-issue-17-sql-sync
- dev-issue-19-better-config-pull
This package is auto-updated.
Last update: 2023-01-18 04:01:01 UTC
README
Robo commands and tasks for Drupal
Doc pages are at https://thinkshout.github.io/robo-drupal/index.html
Classes are listed at https://thinkshout.github.io/robo-drupal/class_think_shout_1_1_robo_drupal_1_1_tasks.html
Update information
If you update to the 3.x release, you will need to rerun robo configure to set the TS_PROD_BRANCH variable (--prod-branch=main). This allows you to use a branch name for production deployments that is not the default. If you do not specify a production branch, it will default to "main".
Once you have set a production branch, you can create a branch with that name from your current production branch, push the new branch up to github, and delete the old branch. In some cases, you may need to change the default branch in github (although that is normally "develop"). You may want to review open pull requests as well, and notify other developers on the project to update their local repositories by pulling down the new branch.