Separate relative path mode for config vs output

[nvx]

Welcome

• Yes, I've searched similar issues on GitHub and didn't find any.
• I agree to follow this project's Code of Conduct

How did you install golangci-lint?

Official GitHub Action

Your feature request related to a problem? Please describe

Specifying a relative path mode of cfg is needed to reliably detect additional config files such as for ruleguard.

Unfortunately this then results in linter outputs using paths relative to the cfg directory too so they start with eg ../../../../../../ breaking CI workflows from referencing the right file

Describe the solution you'd like

A way to specify ruleguard configuration relative to the config directory but path outputs relative to either the working directory, gitroot, or go mod root would fix the issue.

Describe alternatives you've considered

This seemed to work fine under golangci-lint 1.x. Specifying gitroot as the relative-path-mode breaks loading ruleguard rules but output paths are fine, specifying cfg allows ruleguard rules to load fine but output paths are wrong.

Additional context

ruleguard config:

        ruleguard:
          failOn: all
          rules: ${base-path}/ruleguard/*.go

Supporter

• I am a sponsor through GitHub or OpenCollective

[ldez]

Hello,
can you provide a reproducible example?

[nvx]

Hello, can you provide a reproducible example?

I've made a contrived example that demonstrates the issue, you can see the workflow run here with the output paths for a file main.go in the root of the repo instead showing up as ../main.go: https://github.com/nvx/golangci-lint-issue-5646/actions/runs/14119963047

Clicking the link ../main.go L6 results in a 404 page at https://github.com/nvx/golangci-lint-issue-5646/blob/main.go#L6 when the correct path would have been https://github.com/nvx/golangci-lint-issue-5646/blob/main/main.go#L6 if it wasn't for the ../ removing the branch name (in this case main). It also breaks other views where it would normally show the linter outputs alongside the diff etc.

I say contrived example as I'm normally using a reusable action with the config file and rules inside the reusable action repo so normally the path would be the relative path between where the reusable action is checked out and the workspace where the code is checked out leading to a much more complex relative path than just a single ../

[ldez]

Why do you not use the other modes?

Specifying gitroot as the relative-path-mode breaks loading ruleguard rules but output paths are fine

Do you have a reproducible example of this behavior?

[ldez]

I was tricked by the cache.

[nvx]

Why do you not use the other modes?

Specifying gitroot as the relative-path-mode breaks loading ruleguard rules but output paths are fine

Do you have a reproducible example of this behavior?

When trying gitroot with a reusable workflow it failed attempting to load the ruleguard files from the path relative to the gitroot, but in my simple example all in one repo it seems to work. I'm not sure why there is a difference, will try splitting out the action like I have in my real repo and see if I can reproduce it there

[ldez]

The v1 was working only because the report paths where relative to wd.