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

Boxen: Allow provisioning of uncommitted changes #1

Open
radeksimko opened this issue Feb 9, 2015 · 0 comments
Open

Boxen: Allow provisioning of uncommitted changes #1

radeksimko opened this issue Feb 9, 2015 · 0 comments

Comments

@radeksimko
Copy link
Owner

Have a look if boxen has any option how to force it to not ask

Would you like to run Boxen anyway, without the latest updates? [y/N]

and/or automatically answer y.

==> boxen: --> Skipping auto-update, because you've got uncommitted changes:
==> boxen:
==> boxen:  M manifests/site.pp
==> boxen:
==> boxen: Since you've got some uncommitted changes to those files, I'm
==> boxen: going to take the safe road and not automatically update anything.
==> boxen: If you're actively working on some Boxen, maybe you'd like to
==> boxen: switch to a branch, rather than working on master? This way I'll
==> boxen: know that you're trying something new, and won't do things like
==> boxen: automatically update, or submit issues, while you're making
==> boxen: changes. It makes everyone's life a bit easier ❤
==> boxen:
==> boxen: Now, if you *weren't* expecting any changes, here's how to get
==> boxen: back on the golden path:
==> boxen:
==> boxen:   cd /opt/boxen/repo
==> boxen:   git reset --hard origin/master
==> boxen:   boxen
==> boxen:
==> boxen: For more info on how the simple git-based updates work, have a gander at
==> boxen: https://github.com/boxen/our-boxen/blob/master/docs/updates.md
==> boxen:
==> boxen: Would you like to run Boxen anyway, without the latest updates? [y/N]
==> boxen:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant