You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See e.g. the picture below, which is for cms-sw/cmssw#34713, but includes messages also for cms-sw/cmssw#34743. As @perrotta pointed out, both PRs use the same branch (this happens every once in a while). This means that the last "+1" and the github test status are not in sync, which can be confusing.
The text was updated successfully, but these errors were encountered:
@jpata this is known issue. The github statuses (which you see at the end of PR) belongs to the actual commit. So if same commit is used for multiple PRs then github is going to show that status in all PRs. To avoid bot setting the final "test-approved/rejected" status , we use PR number in the status (e.g. cms/34743 and cms/34713). So once all the statuses for PR 34743 have result then bot is going to update only 34743 labels.
See e.g. the picture below, which is for cms-sw/cmssw#34713, but includes messages also for cms-sw/cmssw#34743. As @perrotta pointed out, both PRs use the same branch (this happens every once in a while). This means that the last "+1" and the github test status are not in sync, which can be confusing.
The text was updated successfully, but these errors were encountered: