You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,15 @@ First off, thank you for considering contributing! We simply ask that you follow
4
4
## Pull Requests
5
5
You're free to fork our repository and [open a pull request](../../pulls/) if you'd like to submit a new feature or propose a fix for an unknown issue.
6
6
7
-
Before opening or marking your pull request as ready for review, please be sure to test your build and make sure it is stable and not conflicting with the upstream repository. Try not to diverge from our current code styling and practices in your fork.
7
+
Before opening or marking your pull request as ready for review, please be sure to test your build and make sure it is stable and not conflicting with the upstream repository. Try not to diverge from our current code styling and practices in your branch.
8
8
9
9
### Practices
10
-
The things you should always do and not do when opening a new pull request.
11
-
-**Be clear!** Explain the important details of your changes, if not already obvious.
10
+
The things you should always do and not do when opening a new pull request for this project.
11
+
-**Be clear!** Explain the important details of and motives behind your changes, if not already obvious.
12
12
-**Don't change versioning metadata.** Our maintainers will do that once it's been decided a new update should release soon.
13
-
-**Don't write changelogs.** Maintainers will check back on changes and document everything!
14
-
-**Isolate your changes.** Refrain from formatting or changing code outside of what you're actually working on to prevent conflicts.
15
-
-**Get ready for feedback!** Sometimes not everything done does not meet the standard or is just questionable.
13
+
-**Don't write changelogs.** Maintainers will check back on past changes and document everything!
14
+
-**Isolate your changes.** Refrain from formatting or changing code outside of what you're actually working on in order to prevent conflicts.
15
+
-**Get ready for feedback!** Sometimes not everything done meets the current standard or is just questionable.
16
16
17
17
### Guidelines
18
18
This section mainly covers contributions for new features to Horrible Menu. For other pull requests, we simply ask that you justify your changes in detail when opening your request.
0 commit comments