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
I have my pipeline which refreshes the PR list after every 5sec. Also, it uses the GitHub label "LGTM" to filter the PRs. Now I have PR #1 without the "LGTM" tag. And PR #2 generated after PR1, with LGTM tag.
After the pipeline is refreshed and PR2 is picked by concourse, I added the label "LGTM" to PR#1.
But now the pipeline is not showing PR#1.
This sounds similar to #189. I'm not sure if that would also fix the issue with labels, but I think it might?. We are currently running a version of the resource with #189 merged into it until it is that fix is merged upstream, to avoid similar PR issues with out of order commits.
On our Concourse installation at Gstack, that one is working fine. Could you give a try and provide feedback there?
(the new resource is a drop-in replacement; you only have to switch telia-ossto cfcommunity in in the resource_types: declaration, i.e. specify repository: cfcommunity/github-pr-resource)
I have my pipeline which refreshes the PR list after every 5sec. Also, it uses the GitHub label "LGTM" to filter the PRs. Now I have PR #1 without the "LGTM" tag. And PR #2 generated after PR1, with LGTM tag.
After the pipeline is refreshed and PR2 is picked by concourse, I added the label "LGTM" to PR#1.
But now the pipeline is not showing PR#1.
type: github-pr
source:
repository: *********
access_token: ((token))
labels: ["LGTM"]
check_every: 5m
The text was updated successfully, but these errors were encountered: