From 71da62f95429deb6df8748e0ad2249607740d765 Mon Sep 17 00:00:00 2001 From: Nico Verbruggen Date: Sun, 18 Sep 2022 14:08:10 +0200 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Update=20contribution=20guidelin?= =?UTF-8?q?es?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .github/contributing.md | 23 +++++++++++++++++++++++ .github/pull_request_template.md | 2 +- 2 files changed, 24 insertions(+), 1 deletion(-) create mode 100644 .github/contributing.md diff --git a/.github/contributing.md b/.github/contributing.md new file mode 100644 index 0000000..a1b1f4c --- /dev/null +++ b/.github/contributing.md @@ -0,0 +1,23 @@ +# Contribution Guidelines + +Thank you for your interest in contributing to PHP Monitor. + +I consider this project a bit of a nice side-project to my daily gig, so it is very much a personal affair where I love to tinker around. + +**While the code of the latest PHP Monitor release is public, many things are constantly in flux that may not be pushed to this repository yet.** + +I don't mean to be rude, but I don't want other people involved with the project beyond simply contributing a few small things here and there, as has been the case in the past. + +The extra mental overhead of having additional contributors to report to, whose code will need to be reviewed... it's a lot and it makes working on PHP Monitor less enjoyable for me. + +Plus, at this point, the majority of PHP Monitor's main functionality is also done. + +As a result, I may refer you to this file at some point. Again, I don't wish to be rude, but this general rule stands: + +**Making any changes in a fork and opening a pull request without opening an issue first will most likely result in your PR being closed without mercy.** + +To repeat, I am **not opposed** to small contributions and fixes, if they are **meaningful or insightful**. + +To learn more, please check out the [pull request template](/.github/pull_request_template.md) which contains more information about my contribution requirements. (This will also show up when you open a new PR.) + +Thank you for respecting this! \ No newline at end of file diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 85293b0..3477d27 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -16,7 +16,7 @@ In short: It is usually best to *get in touch first* if you are making substanti ## About destination branches -Please keep in mind that `main` is reserved for the current code state of the latest release and should *never* be the destination branch unless a new release is happening. **Merge requests that target `main` will be closed without mercy.** +Please keep in mind that `main` is reserved for the current code state of the latest release and should *never* be the destination branch unless a new release is happening. **Pull requests that target `main` will be closed without mercy.** Usually, the best target is the stable `dev/x.x` branch that corresponds with the latest major version that is released.