chore: add basic ci tests, publish scaffolding

[toddbaert]

• adds basic build/test
• adds release scaffolding
• adds PR title enforcement for semantic commits
  • this requires all PRs to have semantic titles, for easy inclusion in releases

[gemini-code-assist]

Summary of Changes

Hello @toddbaert, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request establishes foundational development practices by introducing basic CI/build configurations and release scaffolding. It also enhances code quality standards by enforcing semantic commit messages for pull request titles. These changes aim to streamline the development workflow and improve project maintainability.

Highlights

• CI/Build Setup: Basic build and test instructions were added, along with initial scaffolding for continuous integration.
• Release Scaffolding: Initial structures for future release processes have been introduced.
• Semantic Commit Enforcement: Mechanisms for enforcing semantic commit messages in PR titles were added to ensure consistent commit history.
• Documentation Update: The CONTRIBUTING.md file was updated to include the correct command for running tests using Bazel.
• Bzlmod Integration: A WORKSPACE file was added to explicitly state the project's use of Bzlmod for dependency management.

Changelog

• CONTRIBUTING.md
  • Updated the testing instructions to use bazel test //test/....
• WORKSPACE
  • Added a new file to signify the project's adoption of Bzlmod for dependency management.

Ignored Files

• Ignored by pattern: .github/workflows/** (3)
  • .github/workflows/ci-format-test-lint.yml
  • .github/workflows/lint-pr.yml
  • .github/workflows/release-please.yml

Activity

• No specific activity has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request introduces basic CI tests and release scaffolding, along with PR title enforcement for semantic commits. The changes are straightforward and improve the project's development workflow. The CONTRIBUTING.md file is updated to reflect the new test command, and a WORKSPACE file is added for Bazel. Overall, the changes are positive for the project's maintainability and quality.