Thank you for considering contributing to Job Leet! We’re excited to have you help improve the project. To ensure that contributions are smooth and effective, please follow these guidelines:
-
Fork the Repository: Start by creating your own fork of the repository to work on.
-
Create a New Branch: Always create a new branch for each feature or bug fix. Name your branch according to the following convention:
git checkout -b feat/your-name/issue-number
Example:
git checkout -b feat/johndoe/42
-
Make Your Changes: Implement your changes, keeping the following guidelines in mind:
- Create branches from the
main
branch. - Use the format:
feat/your-name/issue-number
for new features orfix/your-name/issue-number
for bug fixes.
- Create branches from the
-
Commit Your Changes: Write clear and concise commit messages, following Conventional Commit Standards.
Example commit message:
git commit -m "feat: Add search functionality for job seekers #42"
For bug fixes:
git commit -m "fix: Handle 404 errors for job search API #21"
-
Testing: Ensure all new functionality is properly tested. Write tests for new features and bug fixes, and ensure existing tests continue to pass.
-
Code Quality: Before pushing your changes, make sure to:
- Follow clean code principles.
- Refactor when necessary to keep the codebase maintainable and efficient.
If you encounter any issues or have suggestions for improvements, please open an issue here and provide clear details about the problem or enhancement.