First off, thank you for considering contributing to this project! Your time and effort are greatly appreciated.
The following is a set of guidelines to help you contribute effectively to the project. Please adhere to these guidelines to make the contribution process smooth and efficient for everyone involved.
This project adheres to the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
If you encounter a bug in the project, feel free to open a bug report. Please include the following details:
- A clear description of the issue.
- Steps to reproduce the bug.
- Information about your environment (OS, browser, Next.js version, etc.).
- Screenshots, if applicable.
If you have an idea for a new feature, we’d love to hear about it! Open a feature request and provide:
- A description of the feature.
- The problem it solves or the value it adds.
- Any alternatives or related features.
When making a contribution through a pull request (PR):
- Fork the repository and create your branch from
main
. - Run the tests to ensure your changes do not break existing code.
- Create your pull request with the following in mind:
- Include a clear description of what the PR changes.
- Reference the issue number your PR is related to (if applicable).
- Ensure that your changes follow the Coding Guidelines.
- Be sure to fill out the provided PR template thoroughly.
-
Clone the repository:
git clone https://github.com/asyrafnorafandi/tournamate.git cd tournamate
-
Install dependencies:
npm install
-
Run the development server:
npm run dev
-
Open your browser and navigate to
http://localhost:3000
to see your changes live.
To ensure consistency across the codebase, please adhere to the following standards:
-
Code Formatting: This project uses Prettier for code formatting. You can run the following command to format your code:
npm run format
-
Linting: Before pushing changes, ensure your code passes linting:
npm run lint
-
Commit Messages: Follow Conventional Commits for commit messages. For example:
fix: resolve navbar alignment issue
feat: add user authentication
Please make sure all tests pass before submitting a PR. If you add new functionality, include corresponding unit/integration tests.
-
Run Tests:
npm test
-
End-to-End Testing: If applicable, ensure your changes work across various environments by adding E2E tests.
Thank you again for your contribution! If you have any questions, feel free to open an issue or reach out to [email protected].