Add CI, release, linting, and contribution configs

[Moustachauve]

Add repository automation and governance files:

• Dependabot config to auto-update GitHub Actions weekly targeting the dev branch;
• Release Drafter template and workflow to draft release notes from dev and categorize PRs;
• a Check workflow that runs xcodebuild unit tests and SwiftLint on macOS runners;
• a .swiftlint.yml with lint rules;
• and CODE_OF_CONDUCT.md and CONTRIBUTING.md to document community standards and branching/PR guidance.

[gemini-code-assist]

Summary of Changes

Hello, 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 significantly enhances the repository's automation and governance by integrating several key configurations. It introduces automated dependency updates for GitHub Actions, streamlines the release process with automated release note generation, and establishes a robust continuous integration pipeline for code quality. Furthermore, it sets clear community standards and provides comprehensive guidelines for contributors, aiming to improve maintainability, collaboration, and overall project health.

Highlights

• Automated Dependency Updates: Configured Dependabot to automatically check for and update GitHub Actions dependencies on a weekly basis, targeting the dev branch.
• Release Automation: Implemented Release Drafter to automate the generation of release notes, categorizing changes based on PR labels and resolving version numbers.
• Continuous Integration (CI) Workflow: Added a CI workflow that runs Xcode unit tests and SwiftLint checks on macOS runners to ensure code quality and stability.
• Code Quality Enforcement: Introduced a .swiftlint.yml configuration file to define specific linting rules, including disabled rules, opt-in rules, and custom thresholds for code complexity and type body length.
• Community Governance: Established a CODE_OF_CONDUCT.md to outline community standards and enforcement procedures, fostering a welcoming and inclusive environment.
• Contribution Guidelines: Provided a CONTRIBUTING.md document detailing the branching strategy, submission process, code quality expectations, PR labeling conventions, and hotfix procedures for contributors.

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/check.yml
  • .github/workflows/release-drafter.yml

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.

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

This pull request introduces several configuration files to automate repository tasks and establish contribution guidelines. The changes are generally well-implemented. My review includes a correction for the release drafter configuration to ensure proper versioning and a recommendation for the SwiftLint configuration to enhance code safety by re-enabling rules that prevent potential runtime crashes.