Best pratices?
- Dominant language
- No language data
- Stars
- 1.9k
- Forks
- 173
- Avg merge
- 10d 13h
- Merged PRs (30d)
- 1
Description
Hi,
I work in a team doing Unity 3D development and I want to enforce good practices for developers. By altering the auto generated .csproj from Unity I can "inject" my .editorconfig and ruleset file and use it seamlessly which I am pretty happy about it.
I found out that dotnet format is a good tool for this as this cover the appearance of the code but also more structural code issues (notably with analyzers especially since we can write our own). As such we have a way to enforce code consistency and raise code quality without much efforts.
The part where I am not sure to go is how to integrate it for the team. Specifically I wonder about the following:
Should everybody run before submitting a PR? If yes, how can I make sure that every formatter would give the same output on everybody computers?
Should a robot do it automatically for everyone, or at least check that you have done it? If so, do you have some example on how dotnet format is integrated in some build pipeline? What would be the best way to make sure that no change are needed? Using ``--verify-no-changes`` or dumping a report (using ``--report``) and parsing it?
And of course, if you have general advice or can share how you use it for your projects I would gladly take those hints :)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.