mirror of
https://github.com/PolyhedralDev/Terra.git
synced 2025-07-18 02:22:32 +00:00
* Fixes #93 Add pull request and issue templates. Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Add CODEOWNERS file Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Fix yaml issues Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> fix yaml?? Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> Fix name of issue template. Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Testing if I can do this with prs too Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> Can I do this with pr templates too?? Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> Can I do this with pr templates too?? Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> Can I do this with pr templates too?? Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Move PULL_REQUEST_TEMPLATE/PULL_REQUEST.md to PULL_REQUEST_TEMPLATE.md, because github :poob: Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * I don't think I can... oof. Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Oops, forgot to add this link. Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Perform requested changes Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Forgot one Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Server software -> Platform & Merge platform + platform version Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Inclusion of "addon" in language Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * compat with other terrain gen mods Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * inclusion of "addon" in FEATURE_REQUEST.md Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Update CODEOWNERS Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * add discord link to config.yml Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * update PULL_REQUEST_TEMPLATE.md to no longer use "plugin" Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Reintroduce stacktrace section Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * be more specific about compat issues Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * modify CODEOWNERS Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Add CODE_OF_CONDUCT.md Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Repo: add CONTRIBUTING.md file Add CONTRIBUTING.md file with some basic guidelines on how to get started contributing. Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Repo: Update git commit types Update git commit types in CONTRIBUTING.md and sort them. Add new entries under "types of changes" for PULL_REQUEST_TEMPLATE.md. Signed-off-by: solonovamax <solonovamax@12oclockpoint.com> * Repo: Performed requested changes forgot some stuff lol Signed-off-by: solonovamax <solonovamax@12oclockpoint.com>
114 lines
5.2 KiB
Markdown
114 lines
5.2 KiB
Markdown
# Pull Request
|
|
|
|
## Brief description.
|
|
|
|
<!-- Please provide a brief description of the goals of your PR -->
|
|
|
|
<!--
|
|
###########################################################################
|
|
## WARNING! ##
|
|
## IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN YOUR PR BEING CLOSED ##
|
|
###########################################################################
|
|
-->
|
|
<!--
|
|
Please go through this checklist item by item and make sure you have successfully completed each of these steps.
|
|
- Your pull request MUST be either on the latest version of Terra, or on a branch for a future release.
|
|
- Make sure that there are no already existing PRs that fix this. If so, it will be closed as a duplicate.
|
|
- Make sure that this change is actually within the scope of Terra and is something a terrain generator should be doing.
|
|
- Make sure that this is not an issue with a specific Terra *pack*, and instead applies to all of Terra.
|
|
- Make sure that you have filled out all the required information and given descriptions of everything.
|
|
-->
|
|
<!-- You can erase any parts of this template not applicable to your Pull Request. -->
|
|
|
|
### What Issues Does This Fix?
|
|
|
|
<!--
|
|
Put Fix #XXXX or Closes #XXXX here if there are any open issues that this PR fixes.
|
|
This is to automatically close the relevant issues.
|
|
You may remove this if there is no issue for this PR.
|
|
But unless this is a very small change, you should make an issue for it.
|
|
-->
|
|
|
|
## Licensing
|
|
|
|
<!-- In order to be accepted, your changes must be under the GPLv3 license. Please check one of the following: -->
|
|
|
|
- [ ] I am the original author of this code, and I am willing to release it under [GPLv3](https://www.gnu.org/licenses/gpl-3.0.en.html).
|
|
- [ ] I am not the original author of this code, but it is in public domain or released
|
|
under [GPLv3](https://www.gnu.org/licenses/gpl-3.0.en.html) or a compatible license.
|
|
<!--
|
|
Please provide reliable evidence of this.
|
|
NOTE: for compatible licenses, you must make sure to add the included license somewhere in the program, if so required.
|
|
(And even if it's not required, it's still nice to do it. Also add attribution somewhere.)
|
|
-->
|
|
|
|
## Goal of the PR
|
|
|
|
<!--
|
|
What is the goal of the PR?
|
|
Put a checklist here of what has been done
|
|
(and what *hasn't*, but you plan to do),
|
|
so we can easily know what was changed.
|
|
Note: this is only required for PRs that add new features.
|
|
If your PR is not adding new features, only fixing bugs or adding translations, then you may delete this section.
|
|
-->
|
|
|
|
- [ ] <!-- First thing -->
|
|
- [ ] <!-- A requirement of the first thing. -->
|
|
- [ ] <!-- A second requirement of the first thing. -->
|
|
- [ ] <!-- Second thing -->
|
|
- [ ] <!-- etc. -->
|
|
|
|
## Affects of the PR
|
|
|
|
<!---
|
|
What types of changes does your code introduce? (Select any that apply. You may select multiple.)
|
|
You must put an x in all the boxes that it applies to. (Like this: [x])
|
|
-->
|
|
|
|
#### Types of changes
|
|
|
|
- [ ] Bug Fix <!-- Anything which fixes an issue in Terra. -->
|
|
- [ ] Build system <!-- Anything which pretain to the build system. -->
|
|
- [ ] Documentation <!-- Anything which adds or improves documentation for existing features. -->
|
|
- [ ] New Feature <!-- Anything which adds new functionality to Terra. -->
|
|
- [ ] Performance <!-- Anything which is imrpoves the performance of Terra. -->
|
|
- [ ] Refactoring <!-- Anything which does not add any new code, only moves code around. -->
|
|
- [ ] Repository <!-- Anything which affects the repository. Eg. changes to the `README.md` file. -->
|
|
- [ ] Revert <!-- Anything which reverts previous commits. -->
|
|
- [ ] Style <!-- Anything which updates style. -->
|
|
- [ ] Tests <!-- Anything which adds or updates tests. -->
|
|
- [ ] Translation <!-- Anything which is internationalizing the Terra program to other languages. -->
|
|
|
|
#### Compatiblity
|
|
|
|
- [ ] Breaking change <!-- A fix, or a feature, that breaks some previous functionality to Terra. -->
|
|
- [ ] Non-Breaking change.
|
|
<!--
|
|
A change which does not break *any* previous functionality of Terra.
|
|
(ie. is backwards compatible and will work with *any* previously existing supported features.
|
|
Note: if a feature is annotated with @Incubating, @Preview, @Experimental,
|
|
or is in a package called something similar to the previous annotations,
|
|
then you may push breaking changes to only THOSE parts of Terra.)
|
|
-->
|
|
|
|
#### Contribution Guidelines.
|
|
|
|
- [ ] I have read the [`CONTRIBUTING.md`](https://github.com/PolyhedralDev/Terra/blob/master/CONTRIBUTING.md) document in the root of the
|
|
git repository.
|
|
- [ ] My code follows the code style for this
|
|
project. <!-- There is an included `.editorconfig` file in the base of the repo. Please use a plugin for your IDE of choice that follows those settings. -->
|
|
|
|
#### Documentation
|
|
|
|
- [ ] My change requires a change to the documentation.
|
|
- [ ] I have updated the documentation accordingly.
|
|
|
|
#### Testing
|
|
|
|
- [ ] I have added tests to cover my changes.
|
|
- [ ] All new and existing tests passed.
|
|
<!--
|
|
If it only introduces small changes, you don't need to add tests.
|
|
But if you add big changes, you should probably at least write *some* testing, where applicable.
|
|
--> |