Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support `.config` project directory

Open
#2,157 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp, powershell
Domain
tooling

Research direction

Start by locating the repository code that resolves the PSScriptAnalyzer configuration path when invoked from a project root, then inspect how explicit config-path overrides are handled. Implement discovery of a config file in .config/ without changing the override behavior, and verify that running PSSA from the project root finds it.

Written by the indexing model from the issue text.

Description

Area - Engine

Summary of the new feature

To declutter a project root directory I'd like the ability to put the PSSA config file inside a .config directy, like suggested here (more details):

One can of course override the config path, but native support for this would be neat.

Proposed technical implementation details (optional)

If running PSSA from project root I'd like it to automatically pick up the config in .config/.

What is the latest version of PSScriptAnalyzer at the point of writing

v1.24.0

Dominant language
C#
Stars
2.2k
Forks
415
Avg merge
13h 1m
Merged PRs (30d)
2

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 PowerShell/PSScriptAnalyzer

All issues in PowerShell/PSScriptAnalyzer

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.