forked from AISaturdaysLagos/Cohort8-Team-Template
-
Notifications
You must be signed in to change notification settings - Fork 3
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 #16 from rileydrizzy/main
Merge
- Loading branch information
Showing
34 changed files
with
321 additions
and
6,051 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
File renamed without changes
File renamed without changes
File renamed without changes
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
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,54 @@ | ||
# Welcome Contributors | ||
|
||
Contributions are what makes the open-source community such an amazing place to learn, inspire, and create. Any contributions you make are **greatly appreciated**. | ||
|
||
We're excited you're interested in contributing to this project! This guide outlines the process for submitting code contributions and provides some helpful tips for getting started. | ||
|
||
## Getting Started | ||
|
||
Before diving in, here are a few things to keep in mind: | ||
|
||
* **Issue Tracking:** We use GitHub issues to track bugs, feature requests, and other project tasks. Before working on a contribution, it's recommended to check the existing issues list and see if there's something you'd like to tackle. This helps avoid duplicate efforts and ensures your contribution aligns with project priorities. | ||
|
||
* **Development Setup:** We recommend following the project's setup instructions to configure your development environment. This ensures you have the necessary tools and dependencies to work on the project. | ||
|
||
## Making a Contribution | ||
|
||
Here's a general workflow for contributing code: | ||
|
||
1. **Fork the Repository:** Click the "Fork" button on the project's main page on GitHub. This creates a copy of the repository in your own account, allowing you to make changes without affecting the original project. | ||
|
||
2. **Clone Your Fork:** Use Git to clone your forked repository to your local machine. This creates a local working directory where you can make changes. | ||
|
||
3. **Create a Branch:** Create a new branch for your specific contribution. This helps keep your changes isolated from the main codebase. Use a descriptive branch name that reflects the nature of your contribution (e.g., "fix-login-bug" or "add-new-feature"). | ||
|
||
EXAMPLE --> (`git checkout -b feature/AmazingFeature`) | ||
|
||
4. **Make Your Changes:** Edit the relevant files and make your code changes. | ||
|
||
5. **Test Changes**: Make your changes and ensure that the code passes all tests. | ||
|
||
6. **Commit Your Changes:** Use Git to commit your changes with clear and concise commit messages. Each commit message should describe what you changed and why. | ||
|
||
EXAMPLE --> (`git commit -m 'Add some AmazingFeature'`) | ||
|
||
7. **Push Your Changes:** Push your commits to your forked repository on GitHub. | ||
|
||
8. **Create a Pull Request:** On GitHub, navigate to your forked repository and create a pull request. This sends a notification to the project maintainers about your proposed changes. | ||
9. **Address Feedback:** Project maintainers may review your pull request and provide feedback or request changes. Be responsive to feedback and make any necessary adjustments. | ||
|
||
## Contribution Guidelines | ||
|
||
* **Code Style:** Follow the project's existing coding style guidelines (e.g., indentation, naming conventions) to ensure consistency. | ||
|
||
* **Testing:** Whenever possible, include unit tests for your code changes. This helps ensure the functionality you added or modified works as expected and doesn't introduce regressions. | ||
|
||
* **Documentation:** If your contribution adds new features or modifies existing functionality, consider updating the project's documentation to reflect the changes. | ||
|
||
## Additional Information | ||
|
||
* **License:** Be sure to understand the project's license before contributing. This clarifies how your code can be used and distributed. | ||
|
||
* **Community:** Feel free to reach out to the project maintainers (if available) if you have any questions or need help with your contribution. | ||
|
||
We appreciate your contributions! By following these guidelines, you can help us make this project even better. |
Empty file.
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
Empty file.
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
File renamed without changes.
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
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
Oops, something went wrong.