[Docs] Fix SkyPilot config path

[Michaelvll]

Tested (run the relevant ones):

• Code formatting: install pre-commit (auto-check on commit) or bash format.sh
• Any manual or new tests for this PR (please specify below)
• All smoke tests: /smoke-test (CI) or pytest tests/test_smoke.py (local)
• Relevant individual tests: /smoke-test -k test_name (CI) or pytest tests/test_smoke.py::test_name (local)
• Backward compatibility: /quicktest-core (CI) or pytest tests/smoke_tests/test_backward_compat.py (local)

[gemini-code-assist]

Summary of Changes

Hello @Michaelvll, 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 focuses on improving the clarity and consistency of SkyPilot's documentation regarding configuration. It updates references to configuration paths, ensuring users are aware of both local and remote configuration options, and enhances internal linking for better documentation navigation.

Highlights

• Configuration Path Clarification: The documentation for SkyPilot's advanced configuration has been updated to explicitly mention both local (~/.sky/config.yaml) and remote (API server dashboard) configuration options, including the URL for the remote dashboard.
• Improved Documentation Linking: In the Kubernetes getting started guide, the reference to the SkyPilot configuration file has been changed from a direct code path to an internal Sphinx reference (:ref:SkyPilot config ``), enhancing consistency and navigability within the documentation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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

This pull request improves the documentation by clarifying the different ways to configure SkyPilot. The change in config.rst adds information about remote configuration through the API server dashboard, and the change in kubernetes-getting-started.rst replaces a hardcoded file path with a more general reference to the configuration documentation. The changes are good, but I've pointed out a minor inconsistency in config.rst that could be addressed to make the documentation even clearer.

[gemini-code-assist]

This is a great addition to clarify that configuration can be done remotely via the API server dashboard. For consistency, you might also want to update the 'Configuration sources and overrides' section below. For example, line 11 still only mentions ~/.sky/config.yaml as the source for global configuration and could be updated to include the remote configuration option.