First off, thank you for considering contributing to Taste of Zimbabwe! It's people like you that make this community such a great place to learn, inspire, and create.
This section guides you through submitting a bug report for Taste of Zimbabwe. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
- Use a clear and descriptive title for the issue to identify the problem.
- Describe the exact steps which reproduce the problem in as many details as possible.
- Provide specific examples to demonstrate the steps.
This section guides you through submitting an enhancement suggestion for Taste of Zimbabwe, including completely new features and minor improvements to existing functionality.
- Use a clear and descriptive title for the issue to identify the suggestion.
- Provide a step-by-step description of the suggested enhancement in as many details as possible.
- Explain why this enhancement would be useful to most Taste of Zimbabwe users.
The process described here has several goals:
- Maintain Taste of Zimbabwe's quality
- Fix problems that are important to users
- Engage the community in working toward the best possible Taste of Zimbabwe
- Fork the repo and create your branch from
main. - If you've added code that should be tested, add tests.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 72 characters or less
- Reference issues and pull requests liberally after the first line
- All JavaScript/TypeScript must adhere to the project's Prettier/ESLint configuration.
This section lists the labels we use to help us track and manage issues and pull requests.
bug- Issues that are bugs.enhancement- Issues that are feature requests.documentation- Issues or PRs related to documentation.