.github/workflows: make codeql a bit quicker

[vdemeester]

Changes

• Use actions/cache to be able to use golang cache (uses **/go.sum to compute the cache hash). This should speed up compilation for any pull-requests that doesn't update dependencies.
• Do not rely on autobuild, but use make binaries to build all binaries.

/cc @afrittoli @chitrangpatel @JeromeJu
/kind misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• Has Tests included if any functionality added or changed
• pre-commit Passed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[vdemeester]

Ah it… fails because, I am adding the binaries target in the same pull-request.. 😅. I could change the Makefile (or the command) in another 🤔

[afrittoli]

Ah it… fails because, I am adding the binaries target in the same pull-request.. 😅. I could change the Makefile (or the command) in another 🤔

Uhm, shouldn't it use the code from the PR?

[vdemeester]

Ah it… fails because, I am adding the binaries target in the same pull-request.. 😅. I could change the Makefile (or the command) in another 🤔

Uhm, shouldn't it use the code from the PR?

Nope, that’s one limitation of GitHub actions and forks. It would run the code from the PR if it is coming from the same repository, but not from a fork. That’s.. a bit of a pain 😅

[vdemeester]

cc @JeromeJu @chitrangpatel

[chitrangpatel]

/lgtm
/approve

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chitrangpatel

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 [chitrangpatel]

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

[JeromeJu]

/retest