Thank you for considering contributing to Dasel! Contributions of all kinds are welcome — whether it's fixing bugs, improving documentation, or adding new features.
-
Check the issue tracker to see if your issue has already been reported.
-
If not, open a new issue with a clear description. Please include:
- Steps to reproduce (if it's a bug)
- Expected vs actual behavior
- Versions of Dasel, Go, and your OS
- Open a discussion if you'd like feedback before implementing.
- If the idea is well-defined, create an issue describing the use case and possible syntax.
-
Fork the repository and clone your fork.
-
Create a new branch for your work:
git checkout -b feature/my-new-feature
-
Make your changes and add tests if relevant.
-
Run the test suite to ensure nothing is broken:
go test ./... -
Commit your changes with a clear message:
git commit -m "Add support for XYZ selector" -
Push your branch and open a Pull Request.
- Follow Go best practices and conventions.
- Keep code simple and readable.
- Add comments for complex logic.
- Ensure documentation requirements are listed on your PR so docs site can be updated.
- Ensure examples are clear and consistent with the style of existing docs.
- Be respectful and constructive in discussions.
- Aim to keep contributions focused and incremental.
If you have questions, feel free to:
- Start a discussion
- Ask in an open issue related to your question
We appreciate your contribution and for helping improve Dasel!