Skip to content

Latest commit

 

History

History
58 lines (43 loc) · 3.38 KB

CONTRIBUTING.md

File metadata and controls

58 lines (43 loc) · 3.38 KB
Raw

Contributing

Thank you for considering contributing to go-TimeTraceDB! Please read these guidelines before submitting a pull request or opening an issue.

Code guidelines

We strive to maintain clean, readable, and maintainable code in go-TimeTraceDB. Please follow these guidelines when contributing code to the project:

  • Code should follow the Effective Go guidelines.
  • Documentation should follow the Go Doc Comments format.
  • Follow the principles of clean code as outlined in Robert C. Martin's "Clean Code" book. Here you can find a summary of the book.
  • Write tests for new code or changes to existing code, and make sure all tests pass before submitting a pull request.
  • Error strings and log messages SHOULD NOT be capitalized (unless beginning with proper nouns or acronyms) and SHOULD NOT end with punctuation. Examples:
    • Correct: "unable to connect to server"
    • Incorrect: "Unable to connect to server"
    • Incorrect: "unable to connect to server."

The following commands are available in the Makefile:

  • make fmt formats the code according to the Go standards.
  • make check runs various checks on the code, including formatting and linting.
  • make test runs the tests to ensure that all functionality is working as intended.

Commit guidelines

Please follow these guidelines when committing changes to go-TimeTraceDB:

  • Each commit should represent a single, atomic change to the codebase. Avoid making multiple unrelated changes in a single commit.
  • Use the Conventional Commits format for commit messages and Pull Request titles.

List of conventional commit types:

Types Description
fix A big fix
feat A new feature
docs Documentation only changes
test Adding missing tests or correcting existing tests
build Changes that affect the build system or external dependencies
ci Changes to our CI configuration files and scripts
perf A code change that improves performance
refactor A code change that neither fixes a bug nor adds a feature
style Changes that do not affect the meaning of the code (white-space, formatting, etc)
chore Other changes that don't modify src or test files

Code of Conduct

This project has adapted the Contributor Covenant, version 2.1 to ensure that our community is welcoming and inclusive for all. Please read it before contributing to the project.

Thank you for your contributions to go-TimeTraceDB!