infra-issues mailing list archives

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

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

Jagadish edited comment on INFRA-15858 at 1/22/18 6:52 PM:
-----------------------------------------------------------

Gotcha. I had a follow-up question. In our current setup, we push to our repo at https://git-wip-us.apache.org/
and it gets mirrored into our Github repo. Could you help us understand how the two repos
will be kept in-sync when we move to Gitbox? 

I can see two options.
1. If a PR is closed and merged from the Github UI, it will be automatically mirrored into
the https://git-wip-us.apache.org/ repo. 
2. Instead, we can rely on the Github repo as the only source of truth and do away with the
git-wip-us.apache.org repo entirely.


was (Author: jagadish1989@gmail.com):
Gotcha. I had a follow-up question. In our current setup, we push to our repo at https://git-wip-us.apache.org/
and it gets mirrored into our Github repo. Could you help us understand how the two repos
will be kept in-sync when we move to Gitbox? 

I can see two options.
1. If a PR is closed and merged from the Github UI, it will be automatically mirrored into
the https://git-wip-us.apache.org/ repo. 
2. Instead, we can rely on the Github repo as the only source of truth and not have the git-wip-us.apache.org
repo itself.

> 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