Skip to content

Commit 2220966

Browse files
committed
docs: update outdate parts of contributing.md
1 parent 990d056 commit 2220966

File tree

1 file changed

+2
-12
lines changed

1 file changed

+2
-12
lines changed

CONTRIBUTING.md

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,6 @@ Contribute to the Telerik NativeScript Command-Line Interface
33

44
*Help us improve the Telerik NativeScript CLI*
55

6-
The Telerik NativeScript CLI lets you create, build, and deploy NativeScript-based projects on iOS and Android devices.
7-
86
* [Report an Issue](#report-an-issue "Learn how to report an issue")
97
* [Request a Feature](#request-a-feature "Learn how to submit a feature or improvement request")
108
* [Contribute to the Code Base](#contribute-to-the-code-base "Learn how to submit your own improvements to the code")
@@ -14,21 +12,13 @@ Report an Issue
1412
===
1513
If you find a bug in the source code or a mistake in the documentation, you can submit an issue to our [GitHub Repository][2].
1614
Before you submit your issue, search the archive to check if a similar issues has been logged or addressed. This will let us focus on fixing issues and adding new features.
17-
If your issue appears to be a bug, and hasn't been reported, open a new issue. To help us investigate your issue and respond in a timely manner, you can provide is with the following details.
18-
19-
* **Overview of the issue:** Provide a short description of the visible symptoms. If applicable, include error messages, screen shots, and stack traces.
20-
* **Motivation for or use case:** Let us know how this particular issue affects your work.
21-
* **Telerik NativeScript version(s):** List the current version and build number of the CLI interface. You can get it by running `tns --version`. Let us know if you have not observed this behavior in earlier versions and if you consider it a regression.
22-
* **System configuration:** Provide us with relevant system configuration information such as operating system, network connection, proxy usage, etc. Let us know if you have been able to reproduce the issue on multiple setups.
23-
* **Steps to reproduce:** If applicable, submit a step-by-step walkthrough of how to reproduce the issue.
24-
* **Related issues:** If you discover a similar issue in our archive, give us a heads up - it might help us identify the culprit.
25-
* **Suggest a fix:** You are welcome to suggest a bug fix or pinpoint the line of code or the commit that you believe has introduced the issue.
15+
If your issue appears to be a bug, and hasn't been reported, open a new issue and select the `Bug report` option. To help us investigate your issue and respond in a timely manner, please follow the recommended bug report template.
2616

2717
[Back to Top][1]
2818

2919
Request a Feature
3020
===
31-
You can request a new feature by submitting an issue with the *feature* label to our [GitHub Repository][2].
21+
You can request a new feature by opening a new issue, selecting the `Feature request` option and following the recommended feature request template.
3222
If you want to implement a new feature yourself, consider submitting it to the [GitHub Repository][2] as a Pull Request.
3323

3424
[Back to Top][1]

0 commit comments

Comments
 (0)