Skip to content

docs: add step-by-step contribution guide for new developers #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Essaba2020 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add step-by-step contribution guide for new developers #41

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -304,3 +304,19 @@ Your contributions help make healthcare better for millions of people across Afr
---

**Together, we can build a healthier future for Africa!** 🩺🌍


## Step-by-Step Contribution Guide

1. Fork this repository to your GitHub account.
2. Clone your fork to your local machine.
3. Create a new branch using a descriptive name e.g. fix/issue-name.
4. Make your changes and test them locally.
5. Commit your changes with a clear message e.g. fix: correct broken link.
6. Push your branch to GitHub.
7. Open a Pull Request referencing the related issue.

## Coding Standards
- Follow PEP 8 style guidelines for Python code.
- Write clear and descriptive commit messages.
- Document any new functions or classes added.