From b521fe4a1fc4348f8de0116ca985fc3c911d29d6 Mon Sep 17 00:00:00 2001 From: Andre_601 <11576465+Andre601@users.noreply.github.com> Date: Fri, 31 Jul 2020 15:24:07 +0200 Subject: [PATCH 01/10] Update Contributing file --- .github/CONTRIBUTING.md | 60 ++++++++--------------------------------- 1 file changed, 11 insertions(+), 49 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 968f6ca..32c08a3 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -1,7 +1,5 @@ [issue]: https://github.com/PlaceholderAPI/PlaceholderAPI/issues/new?template=change_request_placeholderapi.md [Discord]: https://helpch.at/discord -[homepage]: http://contributor-covenant.org -[version]: http://contributor-covenant.org/version/1/4/ # Contributing @@ -11,54 +9,18 @@ Please note we have a code of conduct, please follow it in all your interactions ## Pull Request Process -1. Update the README.md with details of changes if it is affected by those changes. -2. Try to prevent any breaking changes affecting the end-user (Developers using the API). -Mention any breaking changes that could affect the end-user. -3. Document any public methods that the end-user might use. +When creating a Pull request should you follow the below rules: -## Code of Conduct +- When pushing towards the code of PlaceholderAPI make the Pull request target the `develop` branch of this repository. +- When pushing towards the wiki (Towards the dedicated Wiki folder) make the Pull request target the `docs/wiki` branch of this repository. +- Any Pull requests targeting the `master` branch for above reasons will be denied and closed. -### Our Pledge +### Code structure +When changing the code of PlaceholderAPI should you follow these basic guidelines for how to do stuff. -In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. +#### Codestyle +We follow the Google Codestyle for the project. Please make sure that you follow it when contributing code to this project. -### Our Standards - -Examples of behavior that contributes to creating a positive environment -include: - -* Using welcoming and inclusive language -* Being respectful of differing viewpoints and experiences -* Gracefully accepting constructive criticism -* Focusing on what is best for the community -* Showing empathy towards other community members - -Examples of unacceptable behavior by participants include: - -* The use of sexualized language or imagery and unwelcome sexual attention or advances -* Trolling, insulting/derogatory comments, and personal or political attacks -* Public or private harassment -* Publishing others' private information, such as a physical or electronic address, without explicit permission -* Other conduct which could reasonably be considered inappropriate in a professional setting - -### Our Responsibilities - -Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. - -Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. - -### Scope - -This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. - -### Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at our [Discord]. All -complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. - -Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. - -### Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, -available at [http://contributor-covenant.org/version/1/4][version] +#### Documentation +When you implement/change methods that are supposed to be usable by the end-user (developer) is it required to also add or update the corresponding Javadocs of the methods. +Deprecating a method requires you to add a `@deprecated` tag to the comments and mention the next version this may get removed. From fbdd789dbe0e023bea67580ddf0e7025e3b8017a Mon Sep 17 00:00:00 2001 From: Andre_601 <11576465+Andre601@users.noreply.github.com> Date: Fri, 31 Jul 2020 15:26:33 +0200 Subject: [PATCH 02/10] Create CODE_OF_CONDUCT.md --- CODE_OF_CONDUCT.md | 49 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..622ab8f --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,49 @@ +[homepage]: http://contributor-covenant.org +[version]: http://contributor-covenant.org/version/1/4/ + +## Code of Conduct + +### Our Pledge + +In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. + +### Our Standards + +Examples of behavior that contributes to creating a positive environment +include: + +* Using welcoming and inclusive language +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +* The use of sexualized language or imagery and unwelcome sexual attention or advances +* Trolling, insulting/derogatory comments, and personal or political attacks +* Public or private harassment +* Publishing others' private information, such as a physical or electronic address, without explicit permission +* Other conduct which could reasonably be considered inappropriate in a professional setting + +### Our Responsibilities + +Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. + +Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. + +### Scope + +This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. + +### Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at our [Discord]. All +complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. + +### Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, +available at [http://contributor-covenant.org/version/1/4][version] From d12c746630f5b244435442c9c735ea00b4577955 Mon Sep 17 00:00:00 2001 From: Andre_601 <11576465+Andre601@users.noreply.github.com> Date: Fri, 31 Jul 2020 16:00:35 +0200 Subject: [PATCH 03/10] Improve content --- .github/CONTRIBUTING.md | 64 ++++++++++++++++++++++++++++++----------- 1 file changed, 48 insertions(+), 16 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 32c08a3..93960b5 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -1,26 +1,58 @@ -[issue]: https://github.com/PlaceholderAPI/PlaceholderAPI/issues/new?template=change_request_placeholderapi.md +[issue]: https://github.com/PlaceholderAPI/PlaceholderAPI/issues/new [Discord]: https://helpch.at/discord +[Code of Conduct]: https://github.com/PlaceholderAPI/PlaceholderAPI/blob/master/CODE_OF_CONDUCT.md -# Contributing +# Contributing Guidelines +We welcome everyone to contribute towards the PlaceholderAPI Project, but doing so will require you to follow specific rules to keep a consistent and welcoming way of contributing. -When contributing to this repository, please first discuss the change you wish to make via [issue] or through [Discord] with the owners of this repository before making a change. +## Issues +Like any other Project can you encounter bugs or a feature is missing for you in the plugin. +For that can you open an [issue] to report a bug or suggest a new feature to be added. -Please note we have a code of conduct, please follow it in all your interactions with the project. +When doing so, make sure you follow the below rules. -## Pull Request Process +### Follow the Template +We have Issue templates to help us get the required information more easly. Please follow the provided template when either filing a bug report or feature request. +We reserve the right to close your issue without warning for not following the templates. -When creating a Pull request should you follow the below rules: +### Using Latest Version +When it comes to bug reports should you always check first, if you're using the latest release of PlaceholderAPI. +Often is a bug you encounter fixed in a newer release. -- When pushing towards the code of PlaceholderAPI make the Pull request target the `develop` branch of this repository. -- When pushing towards the wiki (Towards the dedicated Wiki folder) make the Pull request target the `docs/wiki` branch of this repository. -- Any Pull requests targeting the `master` branch for above reasons will be denied and closed. +You can optionally also try out development builds to see, if your bug is fixed in those. -### Code structure -When changing the code of PlaceholderAPI should you follow these basic guidelines for how to do stuff. +The same rules apply for when making a feature request. -#### Codestyle -We follow the Google Codestyle for the project. Please make sure that you follow it when contributing code to this project. +### No duplicate issue +Make sure that there isn't any existing issue, which is still open, or is closed with a solution/explanation. +Opening a separate issue for a bug report or feature request, that already exists on the issue tracker only slows down the process of fixing the bug or implementing the feature. -#### Documentation -When you implement/change methods that are supposed to be usable by the end-user (developer) is it required to also add or update the corresponding Javadocs of the methods. -Deprecating a method requires you to add a `@deprecated` tag to the comments and mention the next version this may get removed. +If an issue with the bug or feature you want to report/suggest exists, comment on it with your info (bug reports) or give it a :thumbsup: (Feature Request) to show that this is important for you. + +### Issue isn't caused by external sourced +PlaceholderAPI provides a feature to have extensions (separate jar files) for placeholders. This gives it a possability that an issue you encounter is caused by said extensions or a separate plugin that uses this extension. +In those cases should you report the issue to the issue tracker of the extension or plugin. + +## Pull requests +As an open source project are we welcoming all contributions to improve PlaceholderAPI, being it changes to its code like bug fixes or new features, or contributions to its documentation such as the Wiki or the Javadoc. + +### Code contributions +Any contributions to PlaceholderAPI's code should be done towards the `develop` branch. Targeting the `master` branch in your Pull request may get it closed without warning. +Additionally should you follow the `Google Codestyle` when changing the code and Javadoc. + +Some noteworthy points about Javadoc: + +- `@param` tags are in a single line and any additional param tag after one don't have an empty line in between. +Example: +```java +/** + * @param param1 description + * @param param2 description + */ +``` +- Tags follow the order `@param`, `@return`, `@since` and `@deprecated` +- The `@deprecated` tag should mention the version of when the annotated object will be removed. This usually the next minor version. + +## Code of Conduct +We have a [Code of Conduct] to maintain a welcoming atmosphere in this project. +If your contributions go against the above linked Code of Conduct will we reserve the right t deny or revert your contributions and to permanently remove your access from this project. From c76baeae1c01b806a6bd37afed9a699d219b46b7 Mon Sep 17 00:00:00 2001 From: Andre_601 <11576465+Andre601@users.noreply.github.com> Date: Fri, 31 Jul 2020 16:02:20 +0200 Subject: [PATCH 04/10] Update CONTRIBUTING.md --- .github/CONTRIBUTING.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 93960b5..13d5289 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -1,10 +1,12 @@ [issue]: https://github.com/PlaceholderAPI/PlaceholderAPI/issues/new -[Discord]: https://helpch.at/discord +[discord]: https://helpch.at/discord [Code of Conduct]: https://github.com/PlaceholderAPI/PlaceholderAPI/blob/master/CODE_OF_CONDUCT.md # Contributing Guidelines We welcome everyone to contribute towards the PlaceholderAPI Project, but doing so will require you to follow specific rules to keep a consistent and welcoming way of contributing. +If you have any questions about this contributing file, feel free to contact us on our [Discord Server][discord]. + ## Issues Like any other Project can you encounter bugs or a feature is missing for you in the plugin. For that can you open an [issue] to report a bug or suggest a new feature to be added. From e3d71843ac94321a46b2f97934f870ac82f07294 Mon Sep 17 00:00:00 2001 From: Andre_601 <11576465+Andre601@users.noreply.github.com> Date: Mon, 3 Aug 2020 13:41:35 +0200 Subject: [PATCH 05/10] Fix typos and more info --- .github/CONTRIBUTING.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 13d5289..b63cb85 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -1,6 +1,7 @@ [issue]: https://github.com/PlaceholderAPI/PlaceholderAPI/issues/new [discord]: https://helpch.at/discord [Code of Conduct]: https://github.com/PlaceholderAPI/PlaceholderAPI/blob/master/CODE_OF_CONDUCT.md +[wiki]: https://github.com/PlaceholderAPI/PlaceholderAPI/blob/master/wiki # Contributing Guidelines We welcome everyone to contribute towards the PlaceholderAPI Project, but doing so will require you to follow specific rules to keep a consistent and welcoming way of contributing. @@ -31,8 +32,8 @@ Opening a separate issue for a bug report or feature request, that already exist If an issue with the bug or feature you want to report/suggest exists, comment on it with your info (bug reports) or give it a :thumbsup: (Feature Request) to show that this is important for you. -### Issue isn't caused by external sourced -PlaceholderAPI provides a feature to have extensions (separate jar files) for placeholders. This gives it a possability that an issue you encounter is caused by said extensions or a separate plugin that uses this extension. +### Issue isn't caused by external source +PlaceholderAPI provides a feature to have extensions (separate jar files) for placeholders. This gives it a possability that an issue you encounter is caused by said extensions or a separate plugin that uses those extensions. In those cases should you report the issue to the issue tracker of the extension or plugin. ## Pull requests @@ -53,7 +54,11 @@ Example: */ ``` - Tags follow the order `@param`, `@return`, `@since` and `@deprecated` -- The `@deprecated` tag should mention the version of when the annotated object will be removed. This usually the next minor version. +- The `@deprecated` tag should mention the version of when the annotated object will be removed. This usually would be the next minor version. + +### Wiki/Javadoc contributions +If your Pull request only targets the [wiki] or only changes the Javadoc of PlaceholderAPI (And not its actual code) should Pull requests target the `docs` branch. +The develop branch should only be targeted when you also change some of PlaceholderAPI's code. ## Code of Conduct We have a [Code of Conduct] to maintain a welcoming atmosphere in this project. From 19a80c2d269cb574c3799e031cb09f83e734df86 Mon Sep 17 00:00:00 2001 From: Andre_601 <11576465+Andre601@users.noreply.github.com> Date: Mon, 3 Aug 2020 16:51:46 +0200 Subject: [PATCH 06/10] Do some changes --- .github/CONTRIBUTING.md | 50 +++++++++++++++-------------------------- 1 file changed, 18 insertions(+), 32 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index b63cb85..a13af7e 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -1,65 +1,51 @@ [issue]: https://github.com/PlaceholderAPI/PlaceholderAPI/issues/new [discord]: https://helpch.at/discord -[Code of Conduct]: https://github.com/PlaceholderAPI/PlaceholderAPI/blob/master/CODE_OF_CONDUCT.md +[code of conduct]: https://github.com/PlaceholderAPI/PlaceholderAPI/blob/master/CODE_OF_CONDUCT.md [wiki]: https://github.com/PlaceholderAPI/PlaceholderAPI/blob/master/wiki +[style]: https://github.com/PlaceholderAPI/PlaceholderAPI/tree/master/config/style # Contributing Guidelines We welcome everyone to contribute towards the PlaceholderAPI Project, but doing so will require you to follow specific rules to keep a consistent and welcoming way of contributing. -If you have any questions about this contributing file, feel free to contact us on our [Discord Server][discord]. +If you have any questions about contributions towards the project, feel free to contact us on our [Discord Server][discord]. ## Issues -Like any other Project can you encounter bugs or a feature is missing for you in the plugin. +Like any other project can you encounter bugs or a feature is missing for you in the plugin. For that can you open an [issue] to report a bug or suggest a new feature to be added. When doing so, make sure you follow the below rules. -### Follow the Template -We have Issue templates to help us get the required information more easly. Please follow the provided template when either filing a bug report or feature request. -We reserve the right to close your issue without warning for not following the templates. +### Follow the template +We have issue templates to help us get the required information more easily. Please follow the provided template when either filing a bug report or feature request. +Your issue may be closed without warning for not following the template. -### Using Latest Version -When it comes to bug reports should you always check first, if you're using the latest release of PlaceholderAPI. -Often is a bug you encounter fixed in a newer release. +### Use the latest version +When it comes to bug reports should you always check first, that you're using the latest release of PlaceholderAPI. +Often the bug you've encountered, is fixed in a newer version. -You can optionally also try out development builds to see, if your bug is fixed in those. - -The same rules apply for when making a feature request. +The same rules apply when making a feature request. ### No duplicate issue -Make sure that there isn't any existing issue, which is still open, or is closed with a solution/explanation. +Make sure that there aren't any existing issues relating to the problem, which are still open, or are closed with a solution/explanation. Opening a separate issue for a bug report or feature request, that already exists on the issue tracker only slows down the process of fixing the bug or implementing the feature. If an issue with the bug or feature you want to report/suggest exists, comment on it with your info (bug reports) or give it a :thumbsup: (Feature Request) to show that this is important for you. ### Issue isn't caused by external source -PlaceholderAPI provides a feature to have extensions (separate jar files) for placeholders. This gives it a possability that an issue you encounter is caused by said extensions or a separate plugin that uses those extensions. -In those cases should you report the issue to the issue tracker of the extension or plugin. +PlaceholderAPI provides a feature to have expansions (separate jar files) for placeholders. This gives it a possability that an issue you encounter is caused by said expansions or a separate plugin that uses those expansions. +In those cases should you report the issue to the issue tracker of the expansion or plugin. ## Pull requests -As an open source project are we welcoming all contributions to improve PlaceholderAPI, being it changes to its code like bug fixes or new features, or contributions to its documentation such as the Wiki or the Javadoc. +As an open source project are we welcoming all contributions to improve PlaceholderAPI, being it changes to its code like bug fixes or new features, or contributions to its documentation such as the [Wiki] or the Javadoc. ### Code contributions Any contributions to PlaceholderAPI's code should be done towards the `develop` branch. Targeting the `master` branch in your Pull request may get it closed without warning. -Additionally should you follow the `Google Codestyle` when changing the code and Javadoc. - -Some noteworthy points about Javadoc: - -- `@param` tags are in a single line and any additional param tag after one don't have an empty line in between. -Example: -```java -/** - * @param param1 description - * @param param2 description - */ -``` -- Tags follow the order `@param`, `@return`, `@since` and `@deprecated` -- The `@deprecated` tag should mention the version of when the annotated object will be removed. This usually would be the next minor version. +Additionally should you follow the project's codestyle which you can find in the [`config/style`][style] directory. ### Wiki/Javadoc contributions -If your Pull request only targets the [wiki] or only changes the Javadoc of PlaceholderAPI (And not its actual code) should Pull requests target the `docs` branch. +If your pull request only targets the [wiki] or only changes the javadoc comments of PlaceholderAPI (And not its actual code), it should be to `docs` branch. The develop branch should only be targeted when you also change some of PlaceholderAPI's code. ## Code of Conduct We have a [Code of Conduct] to maintain a welcoming atmosphere in this project. -If your contributions go against the above linked Code of Conduct will we reserve the right t deny or revert your contributions and to permanently remove your access from this project. +If your contributions go against the Code of Conduct, linked above, we reserve the right to deny or revert your contributions. From ec9d6295fb4afdf0a2423aa04a9e74aff6722640 Mon Sep 17 00:00:00 2001 From: Andre_601 <11576465+Andre601@users.noreply.github.com> Date: Mon, 3 Aug 2020 16:56:58 +0200 Subject: [PATCH 07/10] on their? Sounds better imo --- CODE_OF_CONDUCT.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 622ab8f..1a57eb6 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -1,6 +1,8 @@ [homepage]: http://contributor-covenant.org [version]: http://contributor-covenant.org/version/1/4/ +[discord]: https://helpch.at/discord + ## Code of Conduct ### Our Pledge @@ -38,7 +40,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe ### Enforcement -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at our [Discord]. All +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team on their [discord server][discord]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. From d1e30474455216c79d4334590a4a7cacd7dac837 Mon Sep 17 00:00:00 2001 From: Andre_601 <11576465+Andre601@users.noreply.github.com> Date: Mon, 10 Aug 2020 21:29:42 +0200 Subject: [PATCH 08/10] Update CONTRIBUTING.md --- .github/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index a13af7e..153c278 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -43,7 +43,7 @@ Any contributions to PlaceholderAPI's code should be done towards the `develop` Additionally should you follow the project's codestyle which you can find in the [`config/style`][style] directory. ### Wiki/Javadoc contributions -If your pull request only targets the [wiki] or only changes the javadoc comments of PlaceholderAPI (And not its actual code), it should be to `docs` branch. +If your pull request only targets the [wiki] or only changes the javadoc comments of PlaceholderAPI (And not its actual code), it should be to `docs/wiki` branch. The develop branch should only be targeted when you also change some of PlaceholderAPI's code. ## Code of Conduct From 7555bb0f97a268311a854e8ab8e83f9eb1b1fe5c Mon Sep 17 00:00:00 2001 From: Andre_601 <11576465+Andre601@users.noreply.github.com> Date: Wed, 19 Aug 2020 16:27:48 +0200 Subject: [PATCH 09/10] Update .github/CONTRIBUTING.md Co-authored-by: PiggyPiglet --- .github/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 153c278..429786d 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -13,7 +13,7 @@ If you have any questions about contributions towards the project, feel free to Like any other project can you encounter bugs or a feature is missing for you in the plugin. For that can you open an [issue] to report a bug or suggest a new feature to be added. -When doing so, make sure you follow the below rules. +When doing so, make sure you follow rules below: ### Follow the template We have issue templates to help us get the required information more easily. Please follow the provided template when either filing a bug report or feature request. From 18cfd438b84343422ee20210ad7ba420912697a3 Mon Sep 17 00:00:00 2001 From: Andre_601 <11576465+Andre601@users.noreply.github.com> Date: Mon, 31 Aug 2020 03:00:24 +0200 Subject: [PATCH 10/10] Update .github/CONTRIBUTING.md Co-authored-by: PiggyPiglet --- .github/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 429786d..b230db7 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -11,7 +11,7 @@ If you have any questions about contributions towards the project, feel free to ## Issues Like any other project can you encounter bugs or a feature is missing for you in the plugin. -For that can you open an [issue] to report a bug or suggest a new feature to be added. +For that, you can open an [issue] to report a bug, or suggest a new feature to be added. When doing so, make sure you follow rules below: