FAQ
- "What's a pull request?" These are code or documentation contributions to Pneumagination that either fix bugs, improve documentation, or implement new features.)
- "Where do I submit the code?" On the Github Repository. Your pull request there will have its description just link to your post made here. Code goes on GitHub, discussion happens on the forums here.
- "Why separate it?" I want posts to be archived on these forums. This also lets me move the codebase to any Git service I would like in the future without losing any pull request descriptions.
- "What do I do when I have updated the code of my PR?" Update the PR on Github, they describe how to do that. Reply to your PR forum post stating what you have changed, and update the original post if anything needs changing.
- "Am I allowed to post replies to PRs giving opinions on their implementation and such?" Yes, discussion should happen surrounding if a PR should be implemented before it gets merged.
Posting Template:
BE SURE that in your post title you start with either [Bug Fix], [Documentation], or [Enhancement] to describe your PR.
**Tickets:**
Place a bullet list here of links to Bug-Report or Feature-Suggestion posts that relate to your pull request. It is not required to have related bugs or suggestions for your PR, but it can help back up your standing for the code to be implemented.
**Description:**
Describe your code changes and additions here. If your PR relates to a bug report or feature suggestion, describe what you **did** and **did not** implement from it.
**Known Bugs:**
If your PR has known quirks or bugs about its current implementation, note them here.
**Checklist:**
(Check the boxes that apply to your PR. These do not inherently disqualify it from use, just provides helpful info.)
- [ ] I have reviewed and tested my code.
- [ ] I have left comments in my code describing it.
- [ ] My code requires documentation to be changed, and this PR does not include the changed documentation.
- [ ] My code changes a background system that may change how the game is played or its balance.
- [ ] My code directly changes the balance of existing features or how they function.
- [ ] My code adds brand new features that could change the balance of the game.