Skip to content

Fixes to pelican plugin staging #912

Fixes to pelican plugin staging

Fixes to pelican plugin staging #912

name: Linter
on:
push:
tags:
- "*"
branches:
- master
- main
pull_request:
jobs:
linter:
name: linter
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version: '1.21'
cache: false
# We embed the contents of web_ui/frontend/out/* into the resulting binaries
# That particular directory should contain outputs generated by the
# npm build. However, to keep the runtime of the linter as fast as possible,
# instead of running `npm` here, we simply create a dummy empty file.
#
# If no dummy file exists, then the linters will flag the situation as
# an error.
- name: Generate placeholder files
id: generate-placeholder
run: |
go generate ./...
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: "3.9"
# We still run this so that we can get the nice hint of gofmt issues inline
- name: Run golangci-lint
uses: golangci/golangci-lint-action@v4
with:
version: latest
skip-pkg-cache: true
skip-build-cache: true
- name: Run pre-commit
uses: pre-commit/action@v3.0.0