-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #47 from danielcdz/feat-add-contributing-guidelines
Add contribution guidelines
- Loading branch information
Showing
3 changed files
with
60 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
## Pull Request Overview | ||
### 📝 Summary | ||
- Closes #(issue) | ||
- | ||
### 🔄 Changes Made | ||
- | ||
### 🔧 Tests Results | ||
- | ||
|
||
### 🔜 Next Steps | ||
- | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
# Contribution Guidelines | ||
Thank you for considering contributing to this project! We appreciate your time and effort in improving our work. Below are the guidelines to help you contribute effectively. | ||
|
||
# How to Contribute | ||
### 1. Fork the Repository: | ||
Start by forking this repository to your GitHub account. | ||
|
||
### 2. Clone the repository: | ||
After forking, clone the repository to your local machine: | ||
``` bash | ||
git clone https://github.com/your-user/ByteBeastsBackend.git | ||
cd ByteBeastBackend | ||
``` | ||
|
||
### 3. Create a New Branch: | ||
Create a new branch for your feature or bug fix follwing the branch naming convention: | ||
- For bugs: `bug-fix-name` | ||
- For new features: `feat-name` | ||
``` bash | ||
git checkout -b feature-name | ||
``` | ||
|
||
### 4. Make Changes: | ||
Make your changes to the codebase. Ensure your code adheres to the project's coding style and standards. Make sure to add/update tests if needed. | ||
|
||
### 5. Run Tests: | ||
Before submitting your changes, run the existing test suite to ensure your code does not break anything: | ||
``` bash | ||
sozo build | ||
sozo test | ||
``` | ||
|
||
### 6. Commit Your Changes: | ||
Use a descriptive commit message that explains your changes clearly. | ||
|
||
### 7. Push to Your Fork: | ||
Push your changes to your forked repository. | ||
|
||
### 8. Submit a Pull Request | ||
Once your changes are ready, submit a Pull Request (PR) for review. Ensure that: | ||
|
||
- Your PR has a clear and descriptive title. | ||
- You provide a detailed explanation of the changes made. | ||
- You reference any related issues (if applicable). | ||
|
||
All contributions must go through the PR review process to maintain code quality and consistency. A project maintainer will review your PR and provide feedback or merge it into the main branch. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters