Some cleanup

[nlamirault]

No description provided.

[coderabbitai]

Important

Review skipped

More than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review.

80 files out of 193 files are above the max files limit of 100. Please upgrade to Pro plan to get higher limits.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/cleanup

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @nlamirault, 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 undertakes a comprehensive cleanup effort across the repository, primarily focusing on enhancing code readability, standardizing file formats, and removing obsolete components. The changes span documentation, configuration files, and Helm charts, ensuring a more consistent and maintainable codebase. Key improvements include reformatting markdown tables, correcting YAML syntax and indentation, adding SPDX license headers, and eliminating unused chart directories.

Highlights

• Documentation Formatting: Improved readability across numerous README.md files and issue templates by reformatting tables and consolidating multi-line descriptions into single lines.
• YAML Indentation and Syntax Correction: Addressed various indentation issues and corrected string literal usage within YAML configuration files, particularly in Helm chart values and OpenTelemetry collector configurations.
• License Header Standardization: Introduced SPDX license headers to several Helm chart files, promoting open-source compliance and clarity.
• Removal of Obsolete Files: Cleaned up the repository by removing the entire gitops/argocd/charts/monitoring/freebox-exporter directory, including its Chart.yaml, README.md, templates, and values files.
• Git Configuration Refinement: Removed a trailing newline character in the .gitattributes file for consistency.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/cicd-otel.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. ↩

[gemini-code-assist]

Code Review

This pull request contains a large number of cleanup changes across the repository. Most changes involve formatting, adding SPDX license headers, and updating generated documentation files, which improves code consistency and maintainability. I've also noticed the removal of the freebox-exporter chart and some old opentelemetry collector templates. My review includes a couple of suggestions for the markdown issue templates to improve their source readability.

[gemini-code-assist]

While these changes don't affect the rendered output in most markdown viewers, removing the blank lines between sections and between headings and their descriptions reduces the readability of the raw markdown file. It's a good practice to keep these blank lines for better separation and maintainability.

Suggested change

	**Describe the bug** A clear and concise description of what the bug is.
	**To Reproduce**
	Steps to reproduce the behavior:
	**To Reproduce** Steps to reproduce the behavior:
	**Expected behavior**
	A clear and concise description of what you expected to happen.
	**Expected behavior** A clear and concise description of what you expected to
	happen.
	**Screenshots**
	If applicable, add screenshots to help explain your problem.
	**Screenshots** If applicable, add screenshots to help explain your problem.
	**Configuration (please complete the following information):**
	- Kubernetes: [e.g. GKE]
	- Version [e.g. 22]
	**Additional context**
	Add any other context about the problem here.
	**Additional context** Add any other context about the problem here.
	**Describe the bug**
	A clear and concise description of what the bug is.
	**To Reproduce**
	Steps to reproduce the behavior:
	**Expected behavior**
	A clear and concise description of what you expected to happen.
	**Screenshots**
	If applicable, add screenshots to help explain your problem.
	**Configuration (please complete the following information):**
	- Kubernetes: [e.g. GKE]
	- Version [e.g. 22]
	**Additional context**
	Add any other context about the problem here.

[gemini-code-assist]

Similar to the bug report template, removing the blank lines here reduces the readability of the raw markdown. Re-adding them would improve maintainability.

Suggested change

	**Is your feature request related to a problem? Please describe.** A clear and
	concise description of what the problem is. Ex. I'm always frustrated when [...]
	**Describe the solution you'd like**
	A clear and concise description of what you want to happen.
	**Describe the solution you'd like** A clear and concise description of what you
	want to happen.
	**Describe alternatives you've considered**
	A clear and concise description of any alternative solutions or features you've considered.
	**Describe alternatives you've considered** A clear and concise description of
	any alternative solutions or features you've considered.
	**Additional context**
	Add any other context or screenshots about the feature request here.
	**Additional context** Add any other context or screenshots about the feature
	request here.
	**Is your feature request related to a problem? Please describe.**
	A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
	**Describe the solution you'd like**
	A clear and concise description of what you want to happen.
	**Describe alternatives you've considered**
	A clear and concise description of any alternative solutions or features you've considered.
	**Additional context**
	Add any other context or screenshots about the feature request here.