1- # Contributing to `{ name}
2-
3- Welcome! We're thrilled that you're interested in contributing to the
4- `{ name}
5- or contribute code, we appreciate your involvement in making `{ name}
6- better tool for everyone. Here's how you can get started.
7-
8- ## Evangelize
9-
10- One of the simplest ways to help us out is by spreading the word about
11- { name}
12- better framework, and that better frameworks make the world a better
13- place. If you know people who might benefit from using { name}
14- let them know!
15-
16- ## How to Contribute
17-
18- If you're interested in making a more direct contribution, there are
19- several ways you can help us improve { name}
20- for submitting feedback, bug reports, and code contributions.
21-
22- ### Feedback
23-
24- Your feedback is incredibly valuable to us, and we're always looking for
25- ways to make { name}
26- about { name}
27- feedback:
28-
29- - Click [here][2] to submit a new feedback.
30- - Use a descriptive title that clearly summarizes your feedback.
31- - Provide a detailed description of the issue or suggestion.
32- - Be patient while we review and respond to your feedback.
33-
34- ### Bug Reports
35-
36- If you encounter a bug while using { name}
37- fix it. Here's how you can submit a bug report:
38-
39- - Click [here][2] to submit a new issue.
40- - Use a descriptive title that clearly summarizes the bug.
41- - Provide a detailed description of the issue, including steps to
42- reproduce it.
43- - Be patient while we review and respond to your bug report.
44-
45- ### Code Contributions
46-
47- If you're interested in contributing code to { name}
48- have your help! Here's what you need to know:
49-
50- #### Feature Requests
51-
52- If you have an idea for a new feature or improvement, we'd love to hear
53- it. Here's how you can contribute code for a new feature to { name}
54-
55- - Fork the repo.
56- - Clone the { name}
57- `git clone { repository}
58- - Edit files in the `src/` folder. The `src/` folder contains the source
59- code for { name}
60- - Submit a pull request, and we'll review and merge your changes if they
61- fit with our vision for { name}
62-
63- #### Submitting Code
64-
65- If you've identified a bug or have a specific code improvement in mind,
66- we welcome your pull requests. Here's how to submit your code changes:
67-
68- - Fork the repo.
69- - Clone the { name}
70- `git clone { repository}
71- - Edit files in the `src/` folder. The `src/` folder contains the source
72- code for { name}
73- - Submit a pull request, and we'll review and merge your changes if they
74- fit with our vision for { name}
75-
76- We hope that this guide has been helpful in explaining how you can
77- contribute to { name}
78- project!
79-
80- [1]: { repository}
81- [2]: { repository} newHTTP/2 416
1+ # Contributing to `{ name}
2+
3+ Welcome! We're thrilled that you're interested in contributing to the
4+ `{ name}
5+ or contribute code, we appreciate your involvement in making `{ name}
6+ better tool for everyone. Here's how you can get started.
7+
8+ ## Evangelize
9+
10+ One of the simplest ways to help us out is by spreading the word about
11+ { name}
12+ better framework, and that better frameworks make the world a better
13+ place. If you know people who might benefit from using { name}
14+ let them know!
15+
16+ ## How to Contribute
17+
18+ If you're interested in making a more direct contribution, there are
19+ several ways you can help us improve { name}
20+ for submitting feedback, bug reports, and code contributions.
21+
22+ ### Feedback
23+
24+ Your feedback is incredibly valuable to us, and we're always looking for
25+ ways to make { name}
26+ about { name}
27+ feedback:
28+
29+ - Click [here][2] to submit a new feedback.
30+ - Use a descriptive title that clearly summarizes your feedback.
31+ - Provide a detailed description of the issue or suggestion.
32+ - Be patient while we review and respond to your feedback.
33+
34+ ### Bug Reports
35+
36+ If you encounter a bug while using { name}
37+ fix it. Here's how you can submit a bug report:
38+
39+ - Click [here][2] to submit a new issue.
40+ - Use a descriptive title that clearly summarizes the bug.
41+ - Provide a detailed description of the issue, including steps to
42+ reproduce it.
43+ - Be patient while we review and respond to your bug report.
44+
45+ ### Code Contributions
46+
47+ If you're interested in contributing code to { name}
48+ have your help! Here's what you need to know:
49+
50+ #### Feature Requests
51+
52+ If you have an idea for a new feature or improvement, we'd love to hear
53+ it. Here's how you can contribute code for a new feature to { name}
54+
55+ - Fork the repo.
56+ - Clone the { name}
57+ `git clone { repository}
58+ - Edit files in the `src/` folder. The `src/` folder contains the source
59+ code for { name}
60+ - Submit a pull request, and we'll review and merge your changes if they
61+ fit with our vision for { name}
62+
63+ #### Submitting Code
64+
65+ If you've identified a bug or have a specific code improvement in mind,
66+ we welcome your pull requests. Here's how to submit your code changes:
67+
68+ - Fork the repo.
69+ - Clone the { name}
70+ `git clone { repository}
71+ - Edit files in the `src/` folder. The `src/` folder contains the source
72+ code for { name}
73+ - Submit a pull request, and we'll review and merge your changes if they
74+ fit with our vision for { name}
75+
76+ We hope that this guide has been helpful in explaining how you can
77+ contribute to { name}
78+ project!
79+
80+ [1]: { repository}
81+ [2]: { repository} new
0 commit comments