Try add ref to rebase/force push box

[jesserockz]

Description:

Related issue (if applicable): fixes

Pull request in esphome with YAML changes (if applicable): esphome/esphome#

Checklist:

• I am merging into next because this is new documentation that has a matching pull-request in esphome as linked above.
  or

• I am merging into current because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.

• Link added in /index.rst when creating new documents for new components or cookbook.

[netlify]

✅ Deploy Preview for esphome ready!

Name	Link
🔨 Latest commit	704d09d
🔍 Latest deploy log	https://app.netlify.com/sites/esphome/deploys/67186e32c2e8f80008d20f74
😎 Deploy Preview	https://deploy-preview-4372--esphome.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

Walkthrough

The pull request introduces significant modifications to the guides/contributing.rst file for the ESPHome project. It adds new sections to clarify the contribution process, including details on the programming languages used, setting up a development environment, and the review process. Additionally, it provides updated guidelines on submitting pull requests and managing branches, enhancing the overall structure and clarity of the contribution guidelines.

Changes

File	Change Summary
guides/contributing.rst	- Added section: "Contributing to ESPHome" detailing languages and component roles.
	- Expanded section: "Setting Up a Development Environment" with instructions for cloning repos and activating the Python virtual environment.
	- Refined section: "Submitting a Pull Request" to emphasize summary and draft marking.
	- Updated section: "Review Process" to clarify PR review expectations and automated checks.
	- Enhanced section: "Updating Your Branches" with a warning about force-pushing under review.

Possibly related PRs

• [contributing] Various additions & some minor copy fixes/tweaks #4229: This PR also modifies the guides/contributing.rst file, enhancing the contributing guidelines with a restructured review process and new sections, which aligns closely with the changes made in the main PR.
• add collapse and tab examples to guides/contributing.rst #4359: This PR adds examples of collapsible sections and tabs to guides/contributing.rst, directly relating to the enhancements made in the main PR regarding the structure and clarity of the contribution guidelines.

Suggested reviewers

• kbx81: Suggested as a reviewer for this pull request.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 1aa6f36 and 704d09d.

📒 Files selected for processing (1)

• guides/contributing.rst (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

guides/contributing.rst (1)

Pattern **: - Do not generate or add any sequence diagrams

🔇 Additional comments (2)

guides/contributing.rst (2)

780-781: LGTM! Important warning about force pushing.

The warning about force pushing during reviews is well-placed and crucial. It correctly explains the implications of force pushing on the review process and provides appropriate alternatives.

---

Line range hint 1-781: Excellent documentation structure and content.

The documentation is comprehensive, well-organized, and provides clear guidance for contributors. The new sections about contributing to ESPHome, setting up development environments, and the review process are particularly valuable additions.

Key strengths:

• Clear explanation of the project structure and components
• Detailed setup instructions
• Comprehensive review process guidelines
• Well-structured contribution workflow

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.