docs: bump cross-repo links and repo-init branch to trunk-5.5#541
Merged
TangMeng12 merged 1 commit intoMay 11, 2026
Merged
Conversation
tanghao-xiaomi
requested review from
TangMeng12,
aiduxiaoxiong,
smile0425,
xiaoxiang781216 and
yanxingyu17
as code owners
Align doc references with the trunk-5.5 release, mirroring the convention used for the trunk-5.4 tag. - Bump cross-repo URL links (nuttx / nuttx-apps / vendor_* / packages_demos / packages_fe_examples / docs) from /blob|tree/trunk/ to /blob|tree/trunk-5.5/ - Update `repo init -b trunk` commands and surrounding prose in the Ubuntu quick-start guides to use `-b trunk-5.5` - Update patch-version naming example in README from trunk-5.2.1 to trunk-5.5.1 Historical release notes (v5.2.md, v5.4.md), commit-SHA pinned links in the chip-porting guides, the PR template's link to CONTRIBUTING (kept on `trunk` so contributors always see the latest guidelines), and descriptive prose about the `trunk` branch itself are left untouched.
tanghao-xiaomi
force-pushed
the
docs-trunk-tmp
branch
from
c07ea58 to
86397e6
Compare
TangMeng12
approved these changes
May 11, 2026
TangMeng12
approved these changes
May 11, 2026
tanghao-xiaomi
added a commit
to tanghao-xiaomi/docs
that referenced
this pull request
May 12, 2026
Update cross-repository links and repo init commands from the generic `dev` branch to the contest-specific `dev-ai-contest-2026` branch so that references resolve correctly under the current manifest. - blob/dev/<path> -> blob/dev-ai-contest-2026/<path> - tree/dev/<path> -> tree/dev-ai-contest-2026/<path> - repo init -b dev -> repo init -b dev-ai-contest-2026 Follows the same approach as PR open-vela#541 (trunk -> trunk-5.5). Third-party upstream branches (master/main), narrative text about dev/trunk branch strategy, and `/dev/*` device-node paths in code blocks are left untouched.
TangMeng12
pushed a commit
that referenced
this pull request
May 12, 2026
Update cross-repository links and repo init commands from the generic `dev` branch to the contest-specific `dev-ai-contest-2026` branch so that references resolve correctly under the current manifest. - blob/dev/<path> -> blob/dev-ai-contest-2026/<path> - tree/dev/<path> -> tree/dev-ai-contest-2026/<path> - repo init -b dev -> repo init -b dev-ai-contest-2026 Follows the same approach as PR #541 (trunk -> trunk-5.5). Third-party upstream branches (master/main), narrative text about dev/trunk branch strategy, and `/dev/*` device-node paths in code blocks are left untouched.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Align doc references with the trunk-5.5 release, mirroring the convention used for the trunk-5.4 tag.
repo init -b trunkcommands and surrounding prose in the Ubuntu quick-start guides to use-b trunk-5.5Historical release notes (v5.2.md, v5.4.md), commit-SHA pinned links in the chip-porting guides, and descriptive prose about the
trunkbranch itself are left untouched.Note: Please adhere to Contributing Guidelines.
Summary
Update this section with information on why change is necessary,
what it exactly does and how, if new feature shows up, provide
references (dependencies, similar problems and solutions), etc.
Impact
Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.
Testing
Update this section with details on how did you verify the change,
what Host was used for build (OS, CPU, compiler, ..), what Target was
used for verification (arch, board:config, ..), etc. Providing build
and runtime logs from before and after change is highly appreciated.