infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Thistlethwaite (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17401) Out of sync from GitBox to GitHub in a specific branch (branch-2.4)
Date Tue, 11 Dec 2018 22:28:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-17401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718105#comment-16718105
] 

Chris Thistlethwaite commented on INFRA-17401:
----------------------------------------------

Just cleaned up some issues from the migration, can you push another commit to branch-2.4?

> Out of sync from GitBox to GitHub in a specific branch (branch-2.4)
> -------------------------------------------------------------------
>
>                 Key: INFRA-17401
>                 URL: https://issues.apache.org/jira/browse/INFRA-17401
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: GitBox
>            Reporter: Dongjoon Hyun
>            Assignee: Chris Thistlethwaite
>            Priority: Major
>
> Currently, the following branches are out of sync (with two commits).
> https://gitbox.apache.org/repos/asf?p=spark.git;a=shortlog;h=refs/heads/branch-2.4
> https://github.com/apache/spark/commits/branch-2.4
> We did the followings already.
> 1. Wait for the next commit.
> 2. Trigger resync at Apache Selfserv site
> 3. Merge and push directly to GitHub `spark:branch-2.4` (thanks to GitBox
> transition.)
> However, after syncing correctly with (3), the new patches are gone shortly.
> GitHub `spark:branch-2.4` seems to be force-pushed by some other entity.
> Could you give us some instructions on how to fix this?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message