Skip to content

Commit a28bd74

Browse files
committed
bump
Signed-off-by: NishkarshRaj <[email protected]>
1 parent 4b17673 commit a28bd74

File tree

1 file changed

+29
-1
lines changed

1 file changed

+29
-1
lines changed

docs/2_demo.md

Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,34 @@ $ git clone [Repository URL]
8181
$ git log
8282
```
8383

84+
### GitHub Best Practices
85+
86+
`1. Use meaningful commit messages:` Make sure your commit messages are clear and concise, and describe the changes you made in the commit.
87+
88+
`2. Keep your repository organized:` Keep your repository organized by using folders to group related files together. Use descriptive names for your files and folders.
89+
90+
`3. Use branches:` Use branches to work on new features or bug fixes without affecting the main codebase. This allows you to experiment with new ideas without worrying about breaking the main code.
91+
92+
`4. Use pull requests:` Use pull requests to review and merge changes into the main codebase. Pull requests allow you to get feedback on your changes before they are merged into the main codebase.
93+
94+
`5. Use issues:` Use issues to track bugs, feature requests, and other tasks. Issues allow you to track progress and communicate with other contributors.
95+
96+
`6. Use comments and discussions:` Use comments and discussions to communicate with other contributors. This can help you get feedback on your changes and collaborate more effectively.
97+
98+
`7. Use GitHub Actions:` GitHub Actions allow you to automate common tasks, such as running tests or deploying your code. This can help you save time and reduce errors.
99+
100+
`8. Follow best practices for security:` Follow best practices for security, such as using strong passwords, enabling two-factor authentication, and reviewing access permissions regularly.
101+
102+
`9. Keep your repository up-to-date:` Keep your repository up-to-date by pulling in changes from other contributors regularly. This can help you avoid conflicts and ensure that your code is compatible with the latest changes.
103+
104+
`10. Document your code:` Document your code to make it easier for others to understand and use. Use clear and concise comments to describe what your code does, how it works, and any limitations or dependencies.
105+
106+
- [ ] [Readme](https://github.com/NishkarshRaj/Markdown-for-Documentation)
107+
108+
- [ ] [License](https://opensource.org/licenses/)
109+
110+
- [ ] [GitIgnore](https://github.com/github/gitignore)
111+
84112
## Contributing to Upstream GitHub Projects
85113

86114
![Upstream](img/Upstream2.png)
@@ -174,7 +202,7 @@ $ git push
174202

175203
## Important Links and References
176204

177-
[GitHub Learning Labs](https://lab.github.com/)
205+
[GitHub Skills Training](https://skills.github.com/)
178206

179207
[GitHub Upstream Contribution commands cheat sheet](https://statusneo.com/github-upstream-contributions-cheetsheet/)
180208

0 commit comments

Comments
 (0)