Drush commands - Githubissues

beetboxvm / sprintbox

1 stars 1 forks source link

Drush commands #5

Open Decipher opened 8 years ago

Decipher commented 8 years ago

Add some nice drush commands to:

Make a patch (pass in issue number, get out patch)
Reset dev environment (Git reset, git pull, reinstall)

BrianGilbert commented 8 years ago

Make a patch part now to be covered by https://github.com/beetboxvm/ansible-role-beetbox-drush_iq

BrianGilbert commented 8 years ago

@Decipher which reset level did you have in mind? https://git-scm.com/docs/git-reset

Decipher commented 8 years ago

@BrianGilbert gut feeling is --hard

thom8 commented 8 years ago

The most reliable way is to remove and clone during provisioning.

https://github.com/thom8/drupal8-vagrant/blob/master/reset-full.sh

Decipher commented 8 years ago

Not really a viable option on conference network.

On 8 Aug 2016 4:54 PM, "Thom Toogood" notifications@github.com wrote:

The most reliable way is to remove and clone during provisioning.

https://github.com/thom8/drupal8-vagrant/blob/master/reset-full.sh

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/beetboxvm/sprintbox/issues/5#issuecomment-238155454, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJ1QoEdv0S4QED621ylAHZFiCAXosOEks5qdtKRgaJpZM4JeoFK .

thom8 commented 8 years ago

we want the provisioning step to be able to recover from any situation so it might be a git reset if we're using a submodule rather than using the network.