-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
19 additions
and
0 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,19 @@ | ||
## Contributing | ||
|
||
We welcome contributions to ResultAthle! Here's how you can help: | ||
|
||
1. **Fork the Repository:** Start by forking the ResultAthle repository to your own GitHub account. | ||
|
||
2. **Clone the Repository:** Next, clone the repository to your local machine so you can start making changes. | ||
|
||
3. **Create a New Branch:** Make a new branch for your changes. This helps keep everything organized and separates your changes from the main codebase. | ||
|
||
4. **Make Your Changes:** Now you can start making changes to the code. Whether it's fixing a bug, adding a new feature, or improving documentation, your contributions are greatly appreciated! | ||
|
||
5. **Commit Your Changes:** Once you're done making changes, commit them with a clear and concise commit message. | ||
|
||
6. **Push Your Changes:** Push your changes to your forked repository on GitHub. | ||
|
||
7. **Submit a Pull Request:** Finally, submit a pull request so your changes can be reviewed and, if approved, merged into the main codebase. | ||
|
||
Please make sure to follow the project's coding standards and to test your code before submitting a pull request. If you have any questions, feel free to ask! |