Thank you for your interest in contributing to Tech Leadership! This document provides guidelines and instructions for contributing.
Please read and follow our Code of Conduct.
- Check if the bug has already been reported in the Issues section
- If not, create a new issue with a clear title and description
- Include steps to reproduce, expected behavior, and actual behavior
- Add screenshots if applicable
- Check if the feature has already been suggested in the Issues section
- If not, create a new issue with a clear title and description
- Explain why this feature would be useful
- Include any relevant examples or mockups
- Fork the repository
- Create a new branch for your feature/fix
- Make your changes
- Write or update tests as needed
- Update documentation if necessary
- Submit a pull request
- Clone the repository:
git clone https://github.com/carlsendk/tech-leadership.git
cd tech-leadership- Install dependencies:
npm install- Start the development server:
npm run dev- Follow the existing code style
- Use meaningful variable and function names
- Add comments for complex logic
- Keep functions small and focused
- Write tests for new features
- Use clear and descriptive commit messages
- Reference issues and pull requests when applicable
- Follow the conventional commits format:
- feat: A new feature
- fix: A bug fix
- docs: Documentation changes
- style: Code style changes
- refactor: Code refactoring
- test: Adding or updating tests
- chore: Maintenance tasks
By contributing to this project, you agree that your contributions will be licensed under the project's MIT License.