We love your input! We want to make contributing to Docuglean as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Better documentation
- Becoming a maintainer
If this is your first contribution to an Open Source project or you're a core maintainer of multiple projects, your time and interest in contributing to this project is most welcome.
This project follows a Fork/Feature Branch/Pull Request workflow. Here's how it works:
- Fork the project: Create a personal copy of the repository on your GitHub account.
- Clone your fork: Bring a copy of your fork to your local machine.
git clone https://github.com/YOUR_USERNAME/docuglean.git
- Create a new branch: Start a new branch for your changes
git checkout -b feature/your-feature-name
- Make your changes: Implement the changes you wish to contribute.
- Push your changes: Upload your changes to your fork.
git push -u origin feature/your-feature-name
- Create a pull request: Open a new GitHub pull request with the patch against the
mainbranch.- Use semantic commit conventions (e.g.
feat: add new feature,fix: correct issue with X) - Include a clear description of your changes
- Reference any relevant issues
- Use semantic commit conventions (e.g.
- Small changes (< 3 lines): Feel free to submit directly
- Typo fixes
- Documentation updates
- Simple bug fixes
- Larger changes (> 3 lines): Please open an issue first
- New features
- API changes
- Major refactoring
Thank you!
This is an open source project, with an open and welcoming community that is always keen to welcome new contributors.
- GitHub Issues: For bug reports and feature discussions
- Email: Feel free to contact dean@docuglean.com
- Documentation: Check our documentation page
- Community: Join our community forums
Your contributions help make Docuglean better!