Skip to content

Update README #179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

flora-hofmann-frequenz
Copy link
Contributor

No description provided.

Signed-off-by: Flora <[email protected]>
@github-actions github-actions bot added the part:docs Affects the documentation label May 16, 2025
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the README to clarify the instructions for configuring the server URL.

  • Updated the server URL placeholder
  • Adjusted the associated comment for clarity

# Change server address if needed
SERVER_URL = "grpc://reporting.api.frequenz.com:443"
# Change server address
SERVER_URL = "grpc://replace-this-with-your-server-url:port"
Copy link
Preview

Copilot AI May 16, 2025

Choose a reason for hiding this comment

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

[nitpick] Consider adding a brief explanation or example format adjacent to this placeholder to help users understand how to properly update the server URL for their environment.

Copilot uses AI. Check for mistakes.

@flora-hofmann-frequenz flora-hofmann-frequenz added the cmd:skip-release-notes It is not necessary to update release notes for this PR label May 16, 2025
@flora-hofmann-frequenz flora-hofmann-frequenz merged commit c60b4ab into frequenz-floss:v0.x.x May 16, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cmd:skip-release-notes It is not necessary to update release notes for this PR part:docs Affects the documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants