infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15973) Github PRs don't appear to be unique
Date Fri, 02 Feb 2018 20:26:00 GMT

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

Sebb commented on INFRA-15973:
------------------------------

I think the only thing that can be done now is to note that this has happened, i.e. PRs may
not be unique.
A person researching provenance will then know that they need more than just the PR to find
the original info. First match may not be enough.
Otherwise there could be a lot of wasted effort when it is discovered that they have been
working on the wrong PR, which may not be immediately obvious.

> Github PRs don't appear to be unique
> ------------------------------------
>
>                 Key: INFRA-15973
>                 URL: https://issues.apache.org/jira/browse/INFRA-15973
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Github
>            Reporter: Sebb
>            Assignee: Chris Lambertus
>            Priority: Major
>
> Some Github PR numbers have been duplicated.
> This means that the PR cannot be used to uniquely identify the PR.
> This can affect the historical record.
> For example [1] and [2] have the same PR numbers in different years.
> This may be a one-off for this particular git repo.
> Ideally the cause needs to be identified so the problem can be fixed/avoided in future.
> [1] http://mail-archives.apache.org/mod_mbox/lucene-dev/201402.mbox/%3Cgit-pr-30-lucene-solr@git.apache.org%3E
> [2] http://mail-archives.apache.org/mod_mbox/lucene-dev/201604.mbox/%3Cgit-pr-30-lucene-solr@git.apache.org%3E



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

Mime
View raw message