microsoft / microsoft/OpenAPI.NET
avoid regressions for linting improvements
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.6k
- Forks
- 286
- Avg merge
- 6h 38m
- Merged PRs (30d)
- 35
Description
@simoncropp thank you for all the linting and other improvements pull requests (for other readers #1365 through #1398)
I'd like to make sure we don't introduce regressions on those improvements in the future. Hence this issue.
I think we should be able to get all those checked on every PR with:
- editor config with a well configured csharp section
dotnet format --verify-no-changes- editing one of the existing GHA workflows to run this command.
Thoughts? Is this something you'd be willing to submit a PR for once the linting PRs are merged?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing GitHub Actions workflows and the repository's editor configuration first, then run dotnet format --verify-no-changes locally. Done means the relevant editorconfig C# settings and format verification run successfully on every pull request without regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- build-system, ci-cd, developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100