feat(codeTracking): add custom apiEndpoint and token configuration

[AnnatarHe]

Summary

• Add apiEndpoint and token fields to [codeTracking] configuration
• When set, heartbeat data uses these values instead of global configuration
• Allows sending coding activity to a different server or authenticating with a separate token

Test plan

• Added unit tests for custom endpoint/token configuration
• Added tests for partial configuration (only endpoint or only token)
• Added tests for local config override
• All existing tests pass
• Build succeeds

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @AnnatarHe, 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 enhances the codeTracking feature by enabling users to configure a custom API endpoint and authentication token specifically for sending coding activity heartbeats. This allows for more granular control over where and how heartbeat data is transmitted, supporting scenarios where a separate server or authentication mechanism is desired for tracking coding activity, independent of the main application's global settings.

Highlights

• Custom API Endpoint and Token for Code Tracking: Introduced apiEndpoint and token fields within the [codeTracking] configuration section, allowing users to specify a dedicated API endpoint and authentication token for sending coding activity heartbeats.
• Override Global Configuration: When custom apiEndpoint or token values are set under [codeTracking], heartbeat data will utilize these specific values instead of the global application configuration, providing greater flexibility.
• Documentation Update: The docs/CONFIG.md file has been updated to clearly document the new apiEndpoint and token options for codeTracking, including examples and explanations of their purpose.
• Enhanced Test Coverage: New unit tests have been added to model/config_test.go to thoroughly validate the functionality of custom endpoint/token configurations, covering full and partial settings, as well as local configuration overrides.

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. ↩

[codecov]

Codecov Report

❌ Patch coverage is 0% with 9 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
model/api_heartbeat.go	0.00%	9 Missing ⚠️

Flag	Coverage Δ
unittests	19.88% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
model/api_heartbeat.go	0.00% <0.00%> (ø)

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[gemini-code-assist]

Code Review

This pull request introduces a useful feature to allow custom API endpoints and tokens for code tracking heartbeats, overriding the global configuration. The implementation looks solid, with good separation of concerns where the config is read and then used. The changes are well-documented in CONFIG.md and thoroughly tested with new unit tests covering various scenarios, including full, partial, and local override configurations. I've made a few minor suggestions to improve code formatting and test comment clarity, but overall this is a great addition.

[gemini-code-assist]

This comment is slightly misleading. This test correctly verifies that config.CodeTracking.Token is empty when not provided in the config. However, it doesn't test the fallback behavior itself, which happens in SendHeartbeatsToServer. A clearer comment might be // empty, as it's not set in this config to avoid confusion about the scope of this test case.

[gemini-code-assist]

Similar to the previous test case, this comment could be misinterpreted. This test verifies that config.CodeTracking.APIEndpoint is empty, but the fallback to the global endpoint is handled elsewhere. To improve clarity, consider rewording the comment to something like // empty, as it's not set in this config.

[gemini-code-assist]

For consistency with the surrounding code and Go formatting conventions, it's better to have a single space between the struct tag and the line comment. The extra spaces here seem to be a minor formatting artifact.

Suggested change

	Token string `toml:"token"` // Custom token for heartbeats
	Token string `toml:"token"` // Custom token for heartbeats