Environment variable to override default config path

Open Beginner friendly
#6,622 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
64/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
swift
Domain
cli, tooling

Research direction

Start at SwiftLint's CLI handling for the existing --config option and trace how the default swiftlint.yml path is selected. Define the environment-variable behavior alongside that option, including its precedence, then add coverage for the override and verify the CLI still uses its existing default when the variable is absent.

Written by the indexing model from the issue text.

Description

discussion enhancement
New Issue Checklist
Feature or Enhancement Proposal

It would be useful to be able to specify configuration for swiftlint.yml not only via CLI argument, but also via ENV variables, so that they could be set at the CI/mise/dotenv level, so as not to duplicate default parameters every time (not only --config) and not create your own wrappers around swiftlint via the same mise tasks or makefile.

Imho, It seems to be a fairly common practice.

Dominant language
Swift
Stars
19.7k
Forks
2.3k
Avg merge
1d 1h
Merged PRs (30d)
11

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from realm/SwiftLint

All issues in realm/SwiftLint

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.