oras-project/oras-go

ci: enable golangci-lint with a minimal linter set

Closed

#1,286 opened on Aug 2, 2026

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Go (112 forks)auto 404
good first issuehelp wantedv3

Repository metrics

Stars
 (270 stars)
PR merge metrics
 (PR metrics pending)

Description

What

Request adding golangci-lint to CI with a minimal initial linter set, so we get lint signal without a large up-front cleanup. This mirrors the config that was prototyped on the v3 branch (#1130) and has now been pulled out of that PR to keep it scoped to core features.

Proposed config

.golangci.yml:

version: "2"

linters:
  default: none
  enable:
    - govet
    - ineffassign

run:
  go: "1.25"

.github/workflows/lint.yml — a lint job running golangci/golangci-lint-action (v2, e.g. version: v2.11.4) on push/PR to main and v2, with GOFLAGS: -mod=mod.

Makefile — a lint target:

.PHONY: lint
lint:
	GOFLAGS=-mod=mod golangci-lint run

Why minimal

Starting with just govet + ineffassign keeps the initial diff small and CI green, and lets us grow the enabled set incrementally rather than blocking on a big remediation pass.

Contributor guide

Research direction
Examine the existing CI workflow in .github/workflows and how linting is currently handled (if at all). Review the prototype configuration referenced in PR #1130 for context. Then add the .golangci.yml, the lint workflow, and the Makefile target as described in the issue.
Tech stack
github actionsgo
Domain
ci cdbuild systemtooling
Issue type
DevOps
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGoGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80