Skip to content
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

Drush commands #5

Open
Decipher opened this issue Aug 8, 2016 · 6 comments
Open

Drush commands #5

Decipher opened this issue Aug 8, 2016 · 6 comments

Comments

@Decipher
Copy link
Collaborator

Decipher commented Aug 8, 2016

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
Copy link

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

@BrianGilbert
Copy link

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

@Decipher
Copy link
Collaborator Author

Decipher commented Aug 8, 2016

@BrianGilbert gut feeling is --hard

@thom8
Copy link
Member

thom8 commented Aug 8, 2016

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

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

@Decipher
Copy link
Collaborator Author

Decipher commented Aug 8, 2016

Not really a viable option on conference network.

On 8 Aug 2016 4:54 PM, "Thom Toogood" [email protected] 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
#5 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJ1QoEdv0S4QED621ylAHZFiCAXosOEks5qdtKRgaJpZM4JeoFK
.

@thom8
Copy link
Member

thom8 commented Aug 8, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants