[Webkit-unassigned] [Bug 260624] New: [git-webkit] Pushing a branch to a secure remote prevents it from being pushed publicly

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Aug 23 13:23:49 PDT 2023


            Bug ID: 260624
           Summary: [git-webkit] Pushing a branch to a secure remote
                    prevents it from being pushed publicly
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: emw at apple.com

I have a second machine configured as a "secure" remote, so that I can push branches I'm working on to it for testing.

If I push any public branch (i.e. a development branch off `main`) to this remote, I can no longer push the branch publicly. For example:

        > git push bolero eng/dont-mutate-sdk-headers-2 -f
        Pushing to bolero, which is classified as a secure remote

        # test test test, now it's time to open a PR

        > git webkit pr --no-rebase --no-add
        Pushing to fork, which is classified as a public remote
        Verifying commits in 'default' mode
        Attempting to push 1 batch of commits to fork...
        '181f4418c3a3' comes from a more secure remote than 'fork'
        error: failed to push some refs to 'https://github.com/emw-apple/WebKit.git'
        Failed to push 'eng/dont-mutate-sdk-headers-2' to 'fork' (alias of 'https://github.com/emw-apple/WebKit.git')
        Your checkout may be mis-configured, try re-running 'git-webkit setup' or
        your checkout may not have permission to push to 'https://github.com/emw-apple/WebKit.git'

>From what I can tell, git-webkit should care about the *content* of the branch, not its presence on other secure remotes. If I delete my tracking branches:

        > git branch -r --contains eng/dont-mutate-sdk-headers-2 | xargs git branch -dr

then I can push successfully.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230823/dc631ab0/attachment-0001.htm>

More information about the webkit-unassigned mailing list