infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jagadish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15858) Closing PRs in github for Apache Samza
Date Mon, 22 Jan 2018 22:14:01 GMT

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

Jagadish commented on INFRA-15858:
----------------------------------

Thanks Chris for the info. This is helpful. I was curious on how conflicts are dealt with
when mirroring changes between gitbox and github. Assuming both the gitbox and github are
writable repositories, is there any shared synchronization to ensure that two commits don't
end-up in different order on these repos? 

> Closing PRs in github for Apache Samza
> --------------------------------------
>
>                 Key: INFRA-15858
>                 URL: https://issues.apache.org/jira/browse/INFRA-15858
>             Project: Infrastructure
>          Issue Type: Project
>          Components: Github
>            Reporter: Jagadish
>            Assignee: Chris Thistlethwaite
>            Priority: Critical
>
> Hi Infra team,
> I'm a PMC member on the Apache Samza project. Over a period of time, we have had a build
up of pull-requests on github that have been in open state. Some of these PRs are either obsolete,
out-dated and hence, need not be merged. We usually ping contributors to request them to close
these PRs. However, in some cases people don't respond even after repeated pings. This causes
a backlog of PRs that are in "open" state resulting in clutter in our github page. 
> Is there a way for committers or PMC members to close these PRs? I'd really appreciate
guidance on this 



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

Mime
View raw message