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

refs/pull/XXX/merge might not work? #251

Open
tetsuharuohzeki opened this issue Mar 15, 2018 · 4 comments
Open

refs/pull/XXX/merge might not work? #251

tetsuharuohzeki opened this issue Mar 15, 2018 · 4 comments

Comments

@tetsuharuohzeki
Copy link
Contributor

Code

Other mentions

https://blog.bitrise.io/git-clone-step-revision

Update your Git Clone step to 4.0.5 (or higher) as we had it totally rewritten to make it more concise, stable and reliable. Plus it'll be easier to contribute to it in case a new feature is needed. ✨

In case of a Pull Request on GitHub, we cloned the pull request merge branch provided by GitHub (pull//merge), but we had multiple reports of Bitrise using an older state of code without the updates when a build was triggered. This was caused by GitHub's practice of not updating this special branch with every new incoming code update.

https://discuss.bitrise.io/t/git-clone-step-merge-happens-when-manual-merge-is-no/4436

Originally we used the github provided pull/X/merge directly, which includes the pre-merged code directly, but due to recent changes on how/when github updates that branch we had to change that. In short, in the past if you pushed a code change to an open PR the /merge branch was auto updated by github, every time. A couple of months ago github changed this and it’ll now only update the /merge branch if you actually visit the page on the web UI. This means that there’s no point in testing /merge as it might be outdated.

@tetsuharuohzeki
Copy link
Contributor Author

It might be better to revert #156

@tetsuharuohzeki
Copy link
Contributor Author

@nekoya do you have any trouble?

@nekoya
Copy link
Member

nekoya commented Mar 15, 2018

Fmmmm, I don't recognize such troubles in these days.

@tetsuharuohzeki
Copy link
Contributor Author

It might be better to revert #156

The revert is easy. But it would reproduce #140.
To avoid it, we should create auto.tmp or similar tmp branch and ignore it from CI. However, it requires to add auto.tmp as ignored branch for their CI configuration if they uses auto merging.

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

2 participants