-
Notifications
You must be signed in to change notification settings - Fork 3
Reporting Bugs and Contributing
Jeffrey Lester edited this page Dec 4, 2023
·
4 revisions
To report bugs and other issues, please file a GitHub issue. Issues should:
- Contain any relevant log messages (if the bug relates to a command, running
with the
-v
flag will make debugging easier) - Describe what the expected outcome is
- Describe the proposed code fix (optional)
Contributors have two options:
- Fork the repository, then make a PR to merge your changes
- If you have been added as a repository contributor, you can go with the method above or you can create a feature branch, then submit a PR for that feature branch when it is ready to be merged.
In either case, please provide a comprehensive description of your changes with
the PR. PRs will never be merged directly to master
; they are merged into a
release branch. To learn more about PR and release workflows, visit the GitHub
workflows
overview.
If your contribution modifies or adds modules to the library, you must add library tests for all affected modules.
If your contribution modifies the CLI, you must add CLI tests to ensure your changes work.