Add UseConsistentParameterSetName Rule by liamjpeters · Pull Request #2124 · PowerShell/PSScriptAnalyzer

@liamjpeters can you resolve merge conflict please so we can run CI?

Done. If you approve the CI runs, I'll fix any issues that may have cropped up

Thanks for quick turnaround, approved just now. You should be able to run the tests in your fork as well btw (at least that was the case when we were in Azure DevOps before we moved CI to GitHub). If not, let me know, we can look into enabling that generally or just for you as a regular contributor

The triggers for the CI are a push or PR to main. My fork is old enough that it still has master as the default branch and I'm honestly not too sure how to change it 😅. Even still, I probably wouldn't do little PRs for testing on my fork. I can, and do, run the tests locally (on windows at least). It'd need workflow_dispatch as a trigger to enable the "Run Workflow" option in the GUI.

I just updated default branch in my fork to main, you go to settings and rename it here and it then even gives you instructions how to update your local clone, if you didn't want to re-clone. But it's not required for your fork in order to run tests or sync, I've done it with master until now.

In the meantime you should be able to run tests for future work by opening PR in your fork against your fork's default branch but I opened a PR to add workflow_dispatch: #2153