-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mention code formatting in contribution guidelines #5514
Conversation
/* end */ | ||
``` | ||
If you open a pull request and the formatting is incorrect, you can comment | ||
`/format` and a bot will format your code for you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should explain that a PR will be created and you need to merge that PR.
Is there a way to run the formatting my local machine? I personally prefer to get is done before presenting it to others as a review. |
|
||
Open a pull request against `shader-slang/slang`. | ||
|
||
Code formatting can be automatically fixed on your branch by commenting `/format`, a bot will proceed to open a PR targeting *your* branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The formatting is a required process not an optional step. I think we should describe that the generated PR needs to be merged here as Yong pointed out on the other spot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
@jkwak-work You can configure VisualStudio or VSCode to perform formatting on save. In visual studio it is called Code Cleanup: You also need to set code formatter to clang-format. Once configured, you will never need to worry about formatting any more. |
Closes #5511