imported>Rockdtben Нет описания правки |
imported>Rockdtben Нет описания правки |
||
| Строка 5: | Строка 5: | ||
Before you do this, though, we have some requirements so your code doesn't make SS13's infamous spaghetti code problems even worse. Make sure your code fits these requirements or your pull will not be accepted. You may also want to read through the suggestions section. | Before you do this, though, we have some requirements so your code doesn't make SS13's infamous spaghetti code problems even worse. Make sure your code fits these requirements or your pull will not be accepted. You may also want to read through the suggestions section. | ||
== Code Style Requirements == | == 1. Code Style Requirements == | ||
=== Your code MUST compile. === | === Your code MUST compile. === | ||
| Строка 12: | Строка 12: | ||
Warnings should also be cleared, but are not a requirement to fix. | Warnings should also be cleared, but are not a requirement to fix. | ||
=== You MUST follow the coding standards === | === 2. You MUST follow the coding standards === | ||
Please read through these. The standards will change over time. [Coding_Standards] | Please read through these. The standards will change over time. [Coding_Standards] | ||
=== Do not automatically add FILE_DIR. === | === 3. Do not automatically add FILE_DIR. === | ||
A recurring problem that we encounter is people adding commits that needlessly spam changes to the DME due to having "Automatically add FILE_DIR" set in their project settings. You'll know if you have this problem if you see this in your commit (as seen through github): | A recurring problem that we encounter is people adding commits that needlessly spam changes to the DME due to having "Automatically add FILE_DIR" set in their project settings. You'll know if you have this problem if you see this in your commit (as seen through github): | ||
| Строка 29: | Строка 29: | ||
# Close DreamMaker and commit again. | # Close DreamMaker and commit again. | ||
=== Pull Requests Must Be Atomic === | === 4. Pull Requests Must Be Atomic === | ||
Pull requests must add, remove, or change only ONE feature or related group of features. Do not "bundle" together a bunch of things, as each change may be controversial and hold up everything else. In addition, it's simply neater. | Pull requests must add, remove, or change only ONE feature or related group of features. Do not "bundle" together a bunch of things, as each change may be controversial and hold up everything else. In addition, it's simply neater. | ||
| Строка 35: | Строка 35: | ||
=== Follow The Stylesheet. === | === 5. Follow The Stylesheet. === | ||
Changing formatting with \red or other tags is not allowed. You must use span classes, which are defined in interface/stylesheet.dm. | Changing formatting with \red or other tags is not allowed. You must use span classes, which are defined in interface/stylesheet.dm. | ||
Версия от 13:33, 3 июня 2014
Work in progress...
So you've made a change to the code/sprites and want to make a Pull Request so we can add it to the game.
Before you do this, though, we have some requirements so your code doesn't make SS13's infamous spaghetti code problems even worse. Make sure your code fits these requirements or your pull will not be accepted. You may also want to read through the suggestions section.
1. Code Style Requirements
Your code MUST compile.
This is a given. While we will not close your pull request over this, we will not accept it until it does compile cleanly. The Travis bot will check for this automatically, but you should check before you even commit.
Warnings should also be cleared, but are not a requirement to fix.
2. You MUST follow the coding standards
Please read through these. The standards will change over time. [Coding_Standards]
3. Do not automatically add FILE_DIR.
A recurring problem that we encounter is people adding commits that needlessly spam changes to the DME due to having "Automatically add FILE_DIR" set in their project settings. You'll know if you have this problem if you see this in your commit (as seen through github):
PRs that add things to FILE_DIR will be rejected.
To fix this problem:
- Open up DreamMaker
- Build > Preferences for tgstation.dme...
- Uncheck "Automatically set FILE_DIR for sub-directories"
- Check compile.
- Close DreamMaker and commit again.
4. Pull Requests Must Be Atomic
Pull requests must add, remove, or change only ONE feature or related group of features. Do not "bundle" together a bunch of things, as each change may be controversial and hold up everything else. In addition, it's simply neater.
Bugfix-only PRs are exempt from this rule. Everyone loves bugfixes.
5. Follow The Stylesheet.
Changing formatting with \red or other tags is not allowed. You must use span classes, which are defined in interface/stylesheet.dm.
Clearly State What Your Pull Request Does, All Of It
Please do NOT withhold information about your pull request from us. This will get your pull request delayed and if it happens too often your pull request will be closed.
Suppose you fixed bug #1234 and changed the name and description of an item as a gag.
Bad:
In this PR I fixed bug #1234.
Acceptable:
In this PR I fixed bug #1234 and also modified the baton's name and description.