test

[Miki4751]

No description provided.

[github-actions]

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

• maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

• maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change, no action is needed.

---

This is an automated suggestion to help route contributions to the appropriate branch.

[qodo-code-review]

Review Summary by Qodo

Add PR test guide documentation file

📝 Documentation

Walkthroughs

Description

• Add PR test guide documentation file
• Document GitHub PR workflow testing procedures
• Include contributor and test date information

Diagram

flowchart LR
  A["New File"] -- "PR_TEST_GUIDE.md" --> B["Test Guide Documentation"]
  B --> C["GitHub PR Workflow Testing"]

Loading

File Changes

1. PR_TEST_GUIDE.md 📝 Documentation +13/-0

Add GitHub PR workflow test guide

• New documentation file for testing GitHub PR workflow
• Includes test content checklist covering branch creation, file operations, token authentication,
 and PR creation
• Documents contributor information and test date

PR_TEST_GUIDE.md

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX Issues (0)

1. Test artifact committed 🐞 Bug ⚙ Maintainability

Description

PR_TEST_GUIDE.md explicitly states it is only for testing the GitHub PR process, so merging it
leaves a permanent, non-product document at repo root that will confuse users and create maintenance
noise.

Code

PR_TEST_GUIDE.md[R1-4]

+# PR 测试指南
+
+这是一个用于测试 GitHub PR 流程的测试文件。
+

Evidence

The added file self-identifies as a PR-flow test file rather than project documentation. Repo
documentation conventions point developers to use the docs/ tree (especially docs/development) and
the documentation build tooling operates from docs/, making this root-level test guide an orphaned
artifact.

PR_TEST_GUIDE.md[1-4]
docs/policies/CONTRIBUTING.md[19-22]
build_docs.sh[3-53]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A root-level file `PR_TEST_GUIDE.md` is being added even though it explicitly describes itself as a GitHub PR-process test artifact. Keeping such a file in the repository root creates long-lived clutter and is not aligned with the repo’s documentation organization.

## Issue Context
- The file content indicates it is only for PR workflow testing.
- Developer guidance points to using `docs/development` for development-related docs.

## Fix Focus Areas
- PR_TEST_GUIDE.md[1-13]
- docs/policies/CONTRIBUTING.md[19-22]

## Suggested fix
- Preferably: remove `PR_TEST_GUIDE.md` from the PR.
- If you want to keep the guidance: move/rename it into `docs/development/` (and optionally link it from an appropriate doc index) so it’s clearly categorized as developer documentation rather than a root-level artifact.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more