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

Separate the fetch and checkout decisions #1064

Merged
merged 1 commit into from Aug 6, 2019

Conversation

matthewd
Copy link
Contributor

@matthewd matthewd commented Aug 6, 2019

Regardless of how we decide to fetch it, the choice of what to checkout is always the same: FETCH_HEAD if b.Commit is HEAD, and b.Commit otherwise.

Fixes #1063 -- "explicit b.RefSpec supplied" is the only branch whose behaviour is changing here, and only when b.Commit is HEAD.

Regardless of how we decide to fetch it, the choice of what to checkout
is always the same: FETCH_HEAD if b.Commit is HEAD, and b.Commit
otherwise.
Copy link
Member

@sj26 sj26 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great! 🙌

@lox
Copy link
Contributor

lox commented Aug 6, 2019

Why didn't tests run on this? 🤔

@lox
Copy link
Contributor

lox commented Aug 6, 2019

Oh! It's a @matthewd fork.

@lox lox merged commit 9149a7b into buildkite:master Aug 6, 2019
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.

Setting BUILDKITE_REFSPEC when BUILDKITE_COMMIT=HEAD breaks "git checkout"
3 participants