Skip to content

Commit d962261

Browse files
Merge pull request #21 from VirginieLemaire/add_CONTRIBUTING
Added contributing guide
2 parents b06c136 + e1cd83c commit d962261

File tree

2 files changed

+71
-1
lines changed

2 files changed

+71
-1
lines changed

CONTRIBUTING.md

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
# Contributing guide
2+
3+
Thank you for investing your time in contributing to this project!
4+
Please follow this steps :smiley:
5+
6+
## 1. Issues
7+
8+
### Check if an issue exists
9+
10+
If you spot a problem, please [search if an issue already exists](https://github.com/jsvigneshkanna/tailwind_ui_components/issues). If nobody is assigned to this issue, comment the issue to get assigned from maintainers.
11+
12+
### Create a new issue
13+
14+
If it doesn't, you can open a new issue using the [new issue form](https://github.com/jsvigneshkanna/tailwind_ui_components/issues/new/choose) specifying if it's about a bug, a feature, documentation or anything else.
15+
16+
17+
## 2. Fork this repository
18+
19+
Once assigned to an issue, you can fork this repo.
20+
21+
<details>
22+
<summary>Show me how to fork a repository</summary>
23+
Click the **Fork** button on the top right of this repository page
24+
25+
![screenshot of Fork button](https://docs.github.com/assets/cb-23088/images/help/repository/fork_button.png)
26+
27+
It will create a copy of this repository into your account.
28+
29+
Select the owner for the forked repository
30+
![GitHub example](https://docs.github.com/assets/cb-151543/images/help/repository/fork-choose-owner.png)
31+
32+
Choose to **copy only the master branch** and click **Create fork**
33+
</details>
34+
35+
36+
## 3. Clone the fork
37+
38+
Go to your fork repository and clone :
39+
1. `git clone [your repo url goes here]`
40+
2. change directory to your cloned repo `cd [your repo name]`
41+
42+
## 4. Create a new branch and code
43+
44+
**Don't code on the master branch**
45+
46+
Run `git checkout -b [your branch name goes here]` to create your new branch
47+
48+
Make your edits with you favorite IDE
49+
50+
## 5. Save and push
51+
52+
Run `git add .`
53+
54+
Run `git commit -m 'Commit message goes here'` :warning: please commit with an descriptive message for the convenience of reviewer
55+
56+
Finally, run `git push origin [your branch name goes here]`
57+
58+
## 6. Create a pull request (PR)
59+
60+
- Go to your repository in browser and click on compare and pull requests.
61+
- Then add a suitable and crisp title and description to your pull request that explains your contribution.
62+
- Follow the PR template without compromising anything.
63+
- Mention anyone of the reviewers (jsvigneshkanna)
64+
- Voila! Your Pull Request has been submitted and will be reviewed by the moderators and merged.🥳
65+
66+
## 7. Star this repo
67+
68+
Please star this repo to make this project cooler
69+
70+
Happy contributing !

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ free resources to learn or play with these utility based classes
99
If you are searching for an answer for above question/ rant, then this website is best suitable for you all. Here we can get almost all layouts and components built under Tailwind CSS, and the best part is we can play around them in inbuilt code editor and copy the codebase too for your projects
1010

1111
# Like to contribute us by code/ design
12-
Please follow the contributing guide for this repo. Anything that is not followed will not be entertained as contribution.
12+
Please follow the [contributing guide](./CONTRIBUTING.md) for this repo. Anything that is not followed will not be entertained as contribution.
1313

1414
# Like to contribute us by money
1515
This contribution is not forced but welcomed, as this will help us run this software for long time

0 commit comments

Comments
 (0)