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
+44-10Lines changed: 44 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,11 @@
1
1
# Contributing to GitHub-Automation-Scripts
2
-
3
-
First off, thanks for taking the time to contribute! ❤️
4
-
5
-
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
2
+
Ah, thank you ever so much for gracing us with your oh-so-valuable contributions! We're just thrilled to have you here.
3
+
But wait, hold on! Don't just dive in and contribute your precious time. First, read the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
6
4
7
5
> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
8
6
> - Star the project
9
7
> - Tweet about it
10
-
8
+
Remember, every bit of support, big or small, makes a significant difference, and we truly appreciate every gesture of encouragement you offer. Your appreciation fuels our passion for the project, and we're immensely grateful for your involvement in any form! ❤️🌟🐦
11
9
12
10
## Table of Contents
13
11
@@ -30,14 +28,50 @@ If you still feel the need to ask a question and need clarification, we recommen
30
28
31
29
## How To Contribute
32
30
33
-
- Fork the project on GitHub, clone it on your PC.
31
+
To start contributing, follow the guidelines given below:
32
+
33
+
### 1. Fork the Repository
34
+
Fork the repository (https://github.com/sahil-sagwekar2652/GitHub-Automation-scripts)
- If you have an idea for an enhancement or a bug you can first check the [Issues](https://github.com/sahil-sagwekar2652/GitHub-Automation-scripts.git/issues) to see if your question has been asked before.
42
+
35
43
- If you'd like to work on an issue, please ask the creator of the issue to assign it to you. This helps to keep the workflow streamlined.
36
-
- Create a new branch for your contribution and make the changes you want to make. (Always check for updates on the main branch before creating a pull request to avoid merge conflicts.)
44
+
45
+
### 3. Create a New Branch
46
+
```
47
+
git checkout -b <your_branch_name>
48
+
```
49
+
## Making Changes
50
+
Perform your desired changes to the code base.
51
+
52
+
### 4. Track Changes
53
+
```
54
+
git add .
55
+
```
56
+
57
+
### 5. Commit Changes
58
+
```
59
+
git commit -m "Suitable message"
60
+
```
61
+
62
+
### 6. Push Changes
63
+
```
64
+
git push -u origin <your_branch_name>
65
+
```
66
+
67
+
## Creating a Pull Request
68
+
To create a pull request:
69
+
37
70
- The pull request should mention the issue it is trying to solve and should be linked to it. Here is a video on how to link PRs to issues - [video link](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword).
38
-
- Make sure to make the appropriate changes in the README.md file if you are adding a new script or feature.
39
71
72
+
- Make sure to make the appropriate changes in the README.md file if you are adding a new script or feature.
73
+
- Add an appropriate title and description to your pull request, explaining your changes with suitable explanations and screenshots 📝🖼️
74
+
- Click on "Create Pull Request" to submit your contribution for review ✅
40
75
41
76
## Styleguides
42
-
43
-
This project uses the Flake8 linter to lint the Python code. If you are using VSCode, I would suggest installing the [Flake8 linter extension](https://marketplace.visualstudio.com/items?itemName=ms-python.flake8) for VSCode.
77
+
This project uses the Flake8 linter to lint the Python code. If you are using VSCode, I would suggest installing the [Flake8 linter extension](https://marketplace.visualstudio.com/items?itemName=ms-python.flake8) for VSCode.
0 commit comments