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
[VueGen][vuegen-repo] is an open source project, and we welcome contributions of all
4
+
kinds via GitHub issues and pull requests: correct or improve our [documentation][vuegen-docs], report or fix bugs, propose changes, and implement new features. Please follow
5
+
these guidelines to make sure that your contribution is easily integrated into the project.
6
+
7
+
## 1. Contributor Agreement
8
+
9
+
By contributing, you agree that we may redistribute your work under [our
10
+
license](LICENSE). In exchange, we will address your issues and/or assess
11
+
your change proposal as promptly as we can, and help you become a member of our
12
+
community.
13
+
14
+
## 2. What to Contribute
15
+
16
+
The easiest way to get started is by reporting an issue that needs to be fixed,
17
+
such as a bug in the code, unclear explanations, conceptual errors, or other details.
18
+
You can also contribute by proposing new features or modules, improving existing
19
+
functionality, or suggesting other ideas that might be useful. If you’re looking for
20
+
inspiration, please check the [list of open issues][issues] in this repository.
21
+
22
+
Feedback from beginners is especially valuable, as experienced users may overlook how
23
+
challenging certain aspects of the software can be for newcomers. Therefore, we encourage
24
+
you to share any suggestions or observations you have about this project.
25
+
26
+
## 3. How to Contribute
27
+
28
+
Here are the ways you can submit your suggestions and contribute to the project:
29
+
30
+
1.**Reporting Issues or Suggesting Improvements:** If you have a [GitHub][github] account
31
+
(or are willing to [open one][github-join]) but are unfamiliar with Git, you can report
32
+
bugs or suggest improvements by [creating an issue][new-issue]. This GitHub feature allows
33
+
for discussion threads on reported issues and proposed enhancements.
34
+
35
+
2.**Submitting Changes via Pull Requests:** If you are comfortable using Git and would like to
36
+
add or modify a functionality, you can submit a **pull request (PR)**. Instructions on how to contribute this way are provided in the next section.
37
+
38
+
3.**Providing Feedback via Email:** If you don’t have a GitHub account and are
39
+
unfamiliar with Git, you can send feedback via email to [[email protected]][contact]. However, using GitHub is preferred, as it allows us to respond more quickly and track discussions openly.
40
+
41
+
> [!NOTE]
42
+
> The documentation for [Git][git-docs] and [GitHub][github-docs] are easy to follow, and you can learn the basics using their official guides.
43
+
44
+
## 4. Creating a Pull Request
45
+
46
+
If you choose to contribute via GitHub, you may want to look at [How to Contribute to an Open Source Project on GitHub][how-contribute]. In brief, we use [GitHub flow][github-flow] to manage changes:
47
+
48
+
1. Create a new branch in your desktop copy of this repository for each significant change.
49
+
2. Commit the change in that branch.
50
+
3. Push that branch to your fork of this repository on GitHub.
51
+
4. Submit a pull request from that branch to the [upstream repository][vuegen-repo].
52
+
5. If you receive feedback, make changes on your desktop and push to your branch on GitHub: the
53
+
pull request will update automatically.
54
+
55
+
## 5. Credits
56
+
57
+
This contribution guide was modified under the [Creative Commons Attribution 4.0 International License][ccby] from the [Software Carpentry guides][soft-cp-guides].
0 commit comments