Skip to content

Commit 42b1af6

Browse files
authored
Update CONTRIBUTING.md
1 parent 89199f5 commit 42b1af6

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

CONTRIBUTING.md

+3-6
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,14 @@
22

33
We greatly value the feedback and contributions of our users.
44

5-
We keep a distinction between Bugs/Issues, New Features and Support Requests. We also try to minimise the noise in our GitHub Issues stream and prefer having a conversation on [SDKMAN Slack](https://slack.sdkman.io) before creating new issues, if you are not fully sure how to categorize your request. Simply sign up and join one of the following channels:
6-
7-
- User Issues can be raised in our [User Issues channel](https://sdkman.slack.com/app_redirect?channel=user-issues).
8-
- New Features or Enhancements can be discussed in our [CLI Development channel](https://sdkman.slack.com/app_redirect?channel=cli-development).
5+
We distinguish between Bugs/Issues, New Features and Support Requests. We also try to minimise the noise in our GitHub Issues stream and prefer having a conversation on [SDKMAN Discord](https://discord.gg/y9mVJYVyu4) before creating new issues if you are not entirely sure how to categorize your request. Sign up and join our Help channel.
96

107
The [GitHub Issue Tracker](https://github.com/sdkman/sdkman-cli/issues/new) provides templates for required information.
118

12-
**Unfortunately we might simply close any GitHub Issues that have not followed the requested template.**
9+
**Unfortunately, we might close any GitHub Issues that have not followed the requested template.**
1310

1411
### Pull Requests
1512

16-
Pull Requests are _always_ very welcome, but require a valid GitHub Issue as described above. The PR template is to be filled in before submission, ensuring that it is _linked back_ to the GitHub Issue number by replacing `#XXX` with the appropriate issue reference.
13+
Pull Requests are _always_ very welcome but require a valid GitHub Issue as described above. The PR template is to be filled in before submission, ensuring that it is _linked back_ to the GitHub Issue number by replacing `#XXX` with the appropriate issue reference.
1714

1815
Each PR should also be accompanied by a passing test(s) proving its validity (where feasible). The feasibility of the test will emerge in the initial discussions of the issue.

0 commit comments

Comments
 (0)