Skip to content

[8.x](backport #41541) go.mod - use elastic/goja fork #24688

[8.x](backport #41541) go.mod - use elastic/goja fork

[8.x](backport #41541) go.mod - use elastic/goja fork #24688

Workflow file for this run

name: golangci-lint
on:
#push:
# branches:
# - main
# - 8.*
# - 7.17
pull_request:
permissions:
contents: read
# Optional: allow read access to pull request. Use with `only-new-issues` option.
pull-requests: read
jobs:
golangci:
strategy:
matrix:
include:
- GOOS: windows
- GOOS: linux
- GOOS: darwin
name: lint
runs-on: ubuntu-latest
steps:
- name: Echo details
env:
GOOS: ${{ matrix.GOOS }}
run: echo Go GOOS=$GOOS
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version-file: .go-version
- name: Install Apt Package
run: sudo apt-get update && sudo apt-get install -y libpcap-dev librpm-dev
- name: golangci-lint
env:
GOOS: ${{ matrix.GOOS }}
CGO_ENABLED: 1
uses: golangci/golangci-lint-action@v6
with:
# Optional: version of golangci-lint to use in form of v1.2 or v1.2.3 or `latest` to use the latest version
version: v1.55.2
# Give the job more time to execute.
# Regarding `--whole-files`, the linter is supposed to support linting of changed a patch only but,
# for some reason, it's very unreliable this way - sometimes it does not report any or some
# issues without linting the whole files, so we have to use `--whole-files`
# which can lead to some frustration from developers who would like to
# fix a single line in an existing codebase and the linter would force them
# into fixing all linting issues in the whole file instead
args: --timeout=30m --whole-files
# Optional: if set to true then the action will use pre-installed Go.
skip-go-installation: true
# Optional: show only new issues if it's a pull request. The default value is `false`.
only-new-issues: true