Upstream/Waterfall
1
0
Fork 0
mirror of https://github.com/PaperMC/Waterfall.git synced 2024-11-19 08:45:21 +01:00
Code Issues Projects Releases Wiki Activity

fix critical formatting error

Browse Source
This commit is contained in:
kashike 2019-03-17 14:29:47 -07:00 committed by GitHub
parent 03ebf04b65
commit aec375c836
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTING.md
View File

@ -70,7 +70,7 @@ While we will fix minor formatting issues, you should stick to the guide below w
## Formatting ## Formatting
All modifications to non-Waterfall files should be marked All modifications to non-Waterfall files should be marked
- Multi line changes start with `// Waterfall start` and end with `// Waterfall end` - Multi line changes start with `// Waterfall start` and end with `// Waterfall end`
- You can put a messages with a change if it isn't obvious, like this: `// Waterfall start - reason - You can put a messages with a change if it isn't obvious, like this: `// Waterfall start - reason`
- Should generally be about the reason the change was made, what it was before, or what the change is - Should generally be about the reason the change was made, what it was before, or what the change is
- Multi-line messages should start with `// Waterfall start` and use `/* Multi line message here */` for the message itself - Multi-line messages should start with `// Waterfall start` and use `/* Multi line message here */` for the message itself
- Single line changes should have `// Waterfall` or `// Waterfall - reason` - Single line changes should have `// Waterfall` or `// Waterfall - reason`