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

Make sure we are really updating the mercurial repository #31643

Merged

Conversation

opdude
Copy link
Contributor

@opdude opdude commented Mar 3, 2016

What does this PR do?

Fixes a bug in the mercurial state where any changes pulled even if they are not on your branch will claim it as an update to your repo. This also allows you to now switch between branches and run other states based on that change.

What issues does this PR fix or reference?

As above

Previous Behavior

Uses tip to check for the latest revision however tip for mercurial means the latest commit that was pushed no matter which branch its on.

New Behavior

Uses the '.' notation that means the version you are current checked-out with

Tests written?

  • Yes
  • No

This fixes a bug where if you have any changes pushed to a mercurial repo no matter which revision you specify the state will claim the repository is updated. This also correctly detects when you switch from one branch to another in mercurial even if there are no new changes being pulled.
cro added a commit that referenced this pull request Mar 3, 2016
…updated

Make sure we are really updating the mercurial repository
@cro cro merged commit 5566f1f into saltstack:2015.8 Mar 3, 2016
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

Successfully merging this pull request may close these issues.

None yet

2 participants