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
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
## Before creating an issue
4
4
5
5
* Check the [GUIDE](https://www.ditdot.hr/en/docs/vue-flow-form-guide) to see if you can find the solution to your problem by yourself.
6
-
* Check the version of Vue Flow Form you are using - use the last version according to [CHANGELOG](https://github.com/ditdot-dev/vue-flow-form/blob/contributing/CHANGELOG.md).
6
+
* Check the version of Vue Flow Form you are using - use the last version according to [CHANGELOG](https://github.com/ditdot-dev/vue-flow-form/releases).
7
7
* Perform the [Issues](https://github.com/ditdot-dev/vue-flow-form/issues) search to see if the problem has already been reported.
8
8
* If the issue has been reported and is still open, add a comment to it instead of opening a new issue.
9
9
* If the issue has been reported and is closed, open a new issue with a link to the closed issue.
@@ -17,13 +17,13 @@
17
17
18
18
## Suggesting an enhancement
19
19
20
-
* Use a descriptive title and describe the feature request/change in details
21
-
* Explain why this enhancement would be useful
20
+
* Use a descriptive title and describe the feature request/change in details.
21
+
* Explain why this enhancement would be useful.
22
22
23
23
## Creating a pull request
24
24
25
25
* Make your changes on a feature branch. Follow the code style of the project, including indentation.
26
-
* Create a new PR with the code changes
27
-
* The PR description should clearly describe the problem and solution, with a reference to the appropriate issue if applicable
26
+
* Create a new PR with the code changes.
27
+
* The PR description should clearly describe the problem and solution, with a reference to the appropriate issue if applicable.
0 commit comments