Skip to content

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

Description

@tetsuharuohzeki

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions