Kir Kolyshkin 403ea1f088 ci/gha: convert lint-extra from a job to a step ...

There is no need to parallelize lint and lint-extra jobs,
and they only differ with the arguments to golangci-lint.
Given that the longest time spent in these jobs is installing
libseccomp-dev, and that the second linter run can probably
benefit a lot from caching, it makes sense to merge them.

Move lint-extra from a separate job to a step in lint job.

The implementation is motivated by [1] and relies on the fact
that the last commit being fetched is the merge commit. So,
we need to set fetch-depth to 2 to be able to see the diff of
the merge commit -- and this is what golangci-lint is using.

[1] https://github.com/golangci/golangci-lint-action/issues/449#issuecomment-1096995821

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
(cherry picked from commit fa83a17c57)
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>

2023-04-05 10:11:22 -07:00

..

test.yml

Add supported Go releases (1.19, 1.20)

2023-04-05 10:10:53 -07:00

validate.yml

ci/gha: convert lint-extra from a job to a step

2023-04-05 10:11:22 -07:00