-
Notifications
You must be signed in to change notification settings - Fork 420
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
Prevent erroneous remote tracking branch modification by salt.formulas
#238
Comments
myii
added a commit
to myii/salt-formula
that referenced
this issue
Jul 1, 2016
myii
added a commit
to myii/salt-formula
that referenced
this issue
Jul 3, 2016
myii
added a commit
to myii/salt-formula
that referenced
this issue
Aug 19, 2017
aboe76
pushed a commit
that referenced
this issue
Jun 10, 2018
* Ensure options for formulas `git.latest` are also based on defaults * Prevent erroneous remote tracking branch modification by `salt.formulas` #238 * Allow multiple envs to use the same gitdir for `salt.formulas` * Ensure `gitdir` original branch is checked out after formulas `git.latest` * Fix erroneous comment re: merging in `salt` pillar
With the merge of #239, this is now resolved -- closing. |
ixs
pushed a commit
to bawuenet/salt-formula
that referenced
this issue
Jul 22, 2018
…tack-formulas#239) * Ensure options for formulas `git.latest` are also based on defaults * Prevent erroneous remote tracking branch modification by `salt.formulas` saltstack-formulas#238 * Allow multiple envs to use the same gitdir for `salt.formulas` * Ensure `gitdir` original branch is checked out after formulas `git.latest` * Fix erroneous comment re: merging in `salt` pillar
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem definition
Starting point
upstream
branch is currently checked out, which tracksupstream/master
Issue after running
salt.formulas
upstream/master
toorigin/master
Suggested solution
Already understood that this can be avoided by adding the
branch
option to the pillar:However, suggesting to add a conditional block to the
git.latest
state informulas.sls
, setting thebranch: master
option by default, if no specific value set in the pillar:This then avoids the problem outlined above:
Notes
Another side effect of this issue is that the remote tracking branch is set whichever branch is currently checked out, such as a local
dev
branch:Unfortunately becomes:
Happy to submit a PR if approved.
The text was updated successfully, but these errors were encountered: