Skip to content

Conversation

@brombomb
Copy link

@brombomb brombomb commented Nov 4, 2025

Add a changelog generator for the HA updates.

- Add GitHub Action to update changelog based on conventional commits
- Create CONTRIBUTING.md with commit message guidelines
- Add changelog section to README.md
- Set up CHANGELOG.md with proper format
@gemini-code-assist
Copy link

Summary of Changes

Hello @brombomb, I'm Gemini Code Assist1! 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 a robust and automated changelog management system for the project, particularly for Home Assistant updates. It introduces a structured CHANGELOG.md file, a comprehensive CONTRIBUTING.md guide detailing the Conventional Commits standard, and updates the README.md to integrate these new documentation practices. The goal is to streamline release notes and guide contributors on proper commit message formatting for automatic changelog generation.

Highlights

  • Automated Changelog System: This pull request introduces a system for automatic changelog generation, adhering to the Conventional Commits specification for structured commit messages.
  • New Documentation Files: New CHANGELOG.md and CONTRIBUTING.md files have been added to standardize project documentation, track changes, and guide contributors.
  • Project Configuration Updates: The .gitignore file is updated to exclude VS Code specific files, and the README.md is modified to reference the new contributing guidelines and changelog.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/changelog.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.

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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a changelog generation process based on Conventional Commits. It adds a CHANGELOG.md file, a CONTRIBUTING.md with commit guidelines, and updates the README.md to reference these new files. The changes are a great step towards automating release notes and improving contributor experience. I've provided a few suggestions to enhance consistency and fix some minor issues in the new documentation files.

Comment on lines +29 to +56
### Added
- Initial release of TronbytAssistant integration
- Support for Tronbyt device notifications from Home Assistant
- Brightness control via light entity
- Update interval configuration via number entity
- Pinned app selection via select entity
- Night mode toggle via switch entity
- Night mode start/end time configuration
- Night mode brightness and app selection
- Dim mode start time and brightness configuration
- Built-in notification service (Push)
- Custom text notification service (Text)
- App deletion service (Delete)
- Template support for dynamic content
- Argument passing to apps
- HACS integration support
- Configuration flow for easy setup
- Multi-language support (English and German translations)

### Features
- Local polling IoT class for reliable communication
- Single config entry design
- Multi-device support
- Service selectors that update automatically
- Template value support for dynamic content
- HTTP error handling and logging
- Pre-commit hooks for code quality
- Comprehensive test suite

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The CHANGELOG.md file states it's based on Keep a Changelog, but it uses a non-standard Features section. To adhere to the standard, the items under Features should be merged into the Added section, as they represent new functionality added in that release.

### Added
- Initial release of TronbytAssistant integration
- Support for Tronbyt device notifications from Home Assistant
- Brightness control via light entity
- Update interval configuration via number entity
- Pinned app selection via select entity
- Night mode toggle via switch entity
- Night mode start/end time configuration
- Night mode brightness and app selection
- Dim mode start time and brightness configuration
- Built-in notification service (Push)
- Custom text notification service (Text)
- App deletion service (Delete)
- Template support for dynamic content
- Argument passing to apps
- HACS integration support
- Configuration flow for easy setup
- Multi-language support (English and German translations)
- Local polling IoT class for reliable communication
- Single config entry design
- Multi-device support
- Service selectors that update automatically
- Template value support for dynamic content
- HTTP error handling and logging
- Pre-commit hooks for code quality
- Comprehensive test suite


## Manual Workflow Trigger

You can also manually trigger the changelog update by going to the Actions tab and running the "Update Changelog" workflow. No newline at end of file

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

It's a good practice to end text files with a newline character. This prevents issues with some command-line tools and source control systems. Please add a newline at the end of this file.

Suggested change
You can also manually trigger the changelog update by going to the Actions tab and running the "Update Changelog" workflow.
You can also manually trigger the changelog update by going to the Actions tab and running the "Update Changelog" workflow.

Comment on lines +79 to +80
- Development setup
- Pull request process

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The CONTRIBUTING.md file does not yet contain sections for 'Development setup' or 'Pull request process'. To avoid confusion for contributors, it would be best to remove these items from the list for now. They can be added back once the corresponding sections are created in CONTRIBUTING.md.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant