Disposable reviewer-bot validation issue lifecycle run-20260318T215844Z edited

[PLeVasseur]

Disposable validation issue for reviewer-bot post-merge plan scenario: Issue lifecycle and assignment path. Run: run-20260318T215844Z. Edited by issue author during validation.

[github-actions]

👋 Hey @plaindocs! You've been assigned to review this coding guideline issue.

Your Role as Reviewer

As outlined in our contribution guide, please:

1. Provide initial feedback within 14 days

2. Work with @PLeVasseur to flesh out the concept and ensure the guideline is well-prepared for a Pull Request

3. Check the prerequisites before the issue is ready to become a PR:

   • The new rule isn't already covered by another rule
   • All sections contain some content
   • Content written may be incomplete, but must not be incorrect
   • The 🧪 Code Example Test Results section shows all example code compiles

4. When ready, add the sign-off: create pr label to signal the contributor should create a PR

Bot Commands

If you need to pass this review:

• @guidelines-bot /pass [reason] - Pass just this issue to the next reviewer
• @guidelines-bot /away YYYY-MM-DD [reason] - Step away from the queue until a date
• @guidelines-bot /release [@username] [reason] - Release assignment (yours or someone else's with triage+ permission)

To assign someone else:

• @guidelines-bot /r? @username - Assign a specific reviewer
• @guidelines-bot /r? producers - Request the next reviewer from the queue

Other commands:

• @guidelines-bot /claim - Claim this review for yourself
• @guidelines-bot /rectify - Reconcile this issue/PR review state from GitHub
• @guidelines-bot /label +label-name - Add a label
• @guidelines-bot /label -label-name - Remove a label
• @guidelines-bot /queue - Show reviewer queue
• @guidelines-bot /commands - Show all available commands

[github-actions]

📋 RST Preview for Coding Guideline

This is an automatically generated preview of your coding guideline in reStructuredText format.

📁 Target Location

Create a new file:

• src/coding-guidelines//gui_ZHzZl5uJimhf.rst

Create the guideline page like this:

.. SPDX-License-Identifier: MIT OR Apache-2.0
   SPDX-FileCopyrightText: The Coding Guidelines Subcommittee Contributors

.. default-domain:: coding-guidelines

:id: gui_ZHzZl5uJimhf
=====================

.. guideline:: 
    :id: gui_ZHzZl5uJimhf
    :category: 
    :status: 
    :release: -
    :fls: 
    :decidability: 
    :scope: 
    :tags: 



    .. rationale::
        :id: rat_G7t0vCspbyJv
        :status:

🗂️ Update Chapter Index

Ensure src/coding-guidelines//index.rst lists guideline pages with a toctree:

.. toctree::
   :maxdepth: 1
   :titlesonly:
   :glob:

   gui_*

With :glob: you do not need to add the new guideline manually.

📝 How to Use This

1. Fork the repository (if you haven't already) and clone it locally
2. Create a new branch from main:

   git checkout main
   git pull origin main
   git checkout -b guideline/your-descriptive-branch-name

3. Create the guideline directory:

   mkdir -p src/coding-guidelines/

4. Copy the RST content below into a new file named gui_ZHzZl5uJimhf.rst
5. Ensure the chapter index src/coding-guidelines//index.rst contains the toctree block:

    .. toctree::
       :maxdepth: 1
       :titlesonly:
       :glob:
   
       gui_*

   With :glob: you do not need to update the index per guideline.
6. Build locally to verify the guideline renders correctly:

   ./make.py

7. Commit and push your changes:

   git add src/coding-guidelines//
   git commit -m "Add guideline: <your guideline title>"
   git push origin guideline/your-descriptive-branch-name

8. Open a Pull Request against main

📄 Click to expand RST content

.. SPDX-License-Identifier: MIT OR Apache-2.0
   SPDX-FileCopyrightText: The Coding Guidelines Subcommittee Contributors

.. default-domain:: coding-guidelines

:id: gui_ZHzZl5uJimhf
=====================

.. guideline:: 
    :id: gui_ZHzZl5uJimhf
    :category: 
    :status: 
    :release: -
    :fls: 
    :decidability: 
    :scope: 
    :tags: 



    .. rationale::
        :id: rat_G7t0vCspbyJv
        :status:

---

_{🤖 This comment was automatically generated from the issue content. It will be updated when you edit the issue body.}