Handle the case of multiple versions of a status

[afrittoli]

Changes

The GitHub API keeps old versions of a status for historical
reasons. The statuses are returned in reverse chronological
order. This patch pulls-in a version of go-scm that handles
this behaviour and only returns the latest status.

Fixes #2188

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• [n/a] Includes tests (if functionality changed/added)
• [n/a] Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

• If you are adding a new binary/image to the cmd dir, please update
  the release Task to build and release this image.

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

[afrittoli]

@tomgeorge

[dibyom]

/cc @wlynch

[afrittoli]

The go-scm patch is merged, and we have a new release, https://github.com/jenkins-x/go-scm/releases/tag/v1.5.79, so the only change in this patch should be the update to go.mod now.

@tomgeorge I believe this might make your life easier for the label check too.

[afrittoli]

Oh, I need to sync the vendor folder

[ghost]

@bobcatfish just reminded me that we've got the pullrequest Catalog Task now which is pinned to a specific version of the pullrequest-init binary. It's going to be a bit painful until we transition the pullrequest Task away from the binary here but we should probably keep that pinned version up to date as well. PR Task is only on the v1beta1-wip branch at the moment in the catalog (see it here)

[wlynch]

/lgtm
/approve

[afrittoli]

/test pull-tekton-pipeline-integration-tests

[afrittoli]

/test pull-tekton-pipeline-integration-tests

[afrittoli]

@bobcatfish just reminded me that we've got the pullrequest Catalog Task now which is pinned to a specific version of the pullrequest-init binary. It's going to be a bit painful until we transition the pullrequest Task away from the binary here but we should probably keep that pinned version up to date as well. PR Task is only on the v1beta1-wip branch at the moment in the catalog (see it here)

Ack - once this is in the release I will update the catalog task.

[vdemeester]

/lgtm
/meow

[tekton-robot]

@vdemeester:

In response to this:

/lgtm
/meow

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester, wlynch

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[afrittoli]

@vdemeester:

owww, cute

[afrittoli]

/test pull-tekton-pipeline-build-tests

[afrittoli]

/test pull-tekton-pipeline-build-tests

[afrittoli]

@bobcatfish just reminded me that we've got the pullrequest Catalog Task now which is pinned to a specific version of the pullrequest-init binary. It's going to be a bit painful until we transition the pullrequest Task away from the binary here but we should probably keep that pinned version up to date as well. PR Task is only on the v1beta1-wip branch at the moment in the catalog (see it here)

Ack - once this is in the release I will update the catalog task.

tektoncd/catalog#218
@bobcatfish @sbwsg