Skip to content

[8.18](backport #43769) [azure-eventhub] Bump sdk/messaging/azeventhubs to 1.3.1 #31217

[8.18](backport #43769) [azure-eventhub] Bump sdk/messaging/azeventhubs to 1.3.1

[8.18](backport #43769) [azure-eventhub] Bump sdk/messaging/azeventhubs to 1.3.1 #31217

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:
os: [ubuntu-latest, macos-latest, windows-latest]
name: lint
runs-on: ${{ matrix.os }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version-file: .go-version
- name: Install Apt Package
if: runner.os == 'Linux'
run: sudo apt-get update && sudo apt-get install -y libpcap-dev librpm-dev
- name: golangci-lint
env:
CGO_ENABLED: 1
uses: golangci/golangci-lint-action@v7
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: v2.0.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: show only new issues if it's a pull request. The default value is `false`.
only-new-issues: true