You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+23-19
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,29 @@
1
-
# Contributing to CoreUI Free Bootstrap Admin Template
1
+
# Contributing to CoreUI Vue Admin Template
2
2
3
-
Looking to contribute something to CoreUI Free Bootstrap Admin Template? **Here's how you can help.**
3
+
Looking to contribute something? **Here's how you can help.**
4
4
5
5
Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
6
6
7
7
Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
8
8
9
9
## Using the issue tracker
10
10
11
-
The [issue tracker](https://github.com/coreui/coreui-free-vue-bootstrap-admin-template/issues) is the preferred channel for [bug reports](#bug-reports), [features requests](#feature-requests) and [submitting pull requests](#pull-requests), but please respect the following restrictions:
11
+
The [issue tracker](https://github.com/coreui/coreui-free-vue-admin-template/issues) is the preferred channel for [bug reports](#bug-reports), [features requests](#feature-requests) and [submitting pull requests](#pull-requests), but please respect the following restrictions:
12
12
13
-
* Please **do not** use the issue tracker for personal support requests.
13
+
- Please **do not** use the issue tracker for personal support requests.
14
14
15
-
* Please **do not** post comments consisting solely of "+1" or ":thumbsup:".
15
+
- Please **do not** post comments consisting solely of "+1" or ":thumbsup:".
16
16
Use [GitHub's "reactions" feature](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments)
17
17
instead.
18
18
19
-
* Please **do not** open issues or pull requests regarding the code in [`@coreui/coreui`](https://github.com/coreui/coreui) (open them in their respective repositories).
19
+
- Please **do not** open issues or pull requests regarding the code in:
3.**Isolate the problem**— ideally create a [reduced test case](https://css-tricks.com/reduced-test-cases/) and a live example. [This JS Bin](http://jsbin.com/lefey/1/edit?html,output) is a helpful template.
35
42
36
-
37
43
A good bug report shouldn't leave others needing to chase you up for more
38
44
information. Please try to be as detailed as possible in your report. What is
39
45
your environment? What steps will reproduce the issue? What browser(s) and OS
@@ -66,7 +72,6 @@ fits with the scope and aims of the project. It's up to *you* to make a strong
66
72
case to convince the project's developers of the merits of this feature. Please
67
73
provide as much detail and context as possible.
68
74
69
-
70
75
## Pull requests
71
76
72
77
Good pull requests—patches, improvements, new features—are a fantastic
@@ -86,11 +91,11 @@ included in the project:
86
91
87
92
```bash
88
93
# Clone your fork of the repo into the current directory
2. If you cloned a while ago, get the latest changes from upstream:
@@ -133,14 +138,13 @@ included in the project:
133
138
134
139
Inspired by Sparkbox's awesome article on [semantic commit messages](http://seesparkbox.com/foundry/semantic_commit_messages). Please use following commit message format.
135
140
136
-
* chore (updating npm tasks etc; no production code change) -> ```git test -m 'chore: commit-message-here'```
0 commit comments