Index of every page on this site: llms.txt
All skills
microsoft avatar

/nvx-rebase-openvmm-chain

@fef56ac
by microsoftmicrosoft/nvx857 stars
66
Run it yourself

Rebase or reorganize the OpenVMM microVM chain onto the latest upstream main as a new feature/microvm/release branch, validate and publish it, pin it in NVX with a remapped roadmap, and land it. Use for microVM release rebases and reorganizations, chain commits that upstream landed, rebase conflicts and fixups, and the release landing order.

  • 2 files
  • 12.9 KB
  • Updated 4 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/microsoft/nvx/nvx-rebase-openvmm-chain

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesremap.md

≈456 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Remapping The OpenVMM Roadmap Onto A Release

A release moves every commit of the chain, so the NVX pull request that pins it remaps the whole roadmap. Derive each number from Git, as python3 scripts/openvmm_pin.py roadmap does, and check every position and SHA against git -C openvmm rev-list --reverse NEW_BASE..NEW_HEAD. Follow each part's current wording and table headers, and update:

  • Scope: the new fork base, its date, and the base before it; the SHAs and positions of the mapped tip and the pin; the pin's distance from the mapped tip; and the positions not yet assigned to PRs.
  • Upstream status: a first paragraph that says which chain moved from which base onto which, how many upstream commits later, and what the release dropped, resolved, and added.
  • Landed upstream: a row for each drop, with the release's version, and the branch that the release started from in the sentence after the table.
  • Open upstream pull requests: each pull request's state, queried again, as of the date.
  • Conflicts: a Conflicts of the VERSION rebase table with each conflict's position, its commit, the previous release's commit, the upstream pull request, and the resolution; for a reorganization, also a The VERSION reorganization section that says where each fix went.
  • Upstream main past the fork base: upstream's commits after the new base, and those that conflict with the chain.
  • The dependency graph, the actual branch DAG, the commits after the mapped tip with each one's position in the previous release, the PR summary, and the exact commit-to-PR mapping.

Then run python3 scripts/openvmm_pin.py check-roadmap --worktree, which checks the Scope, the DAG, the table, and the commit mapping against Git.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at fef56ac. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 7 hours ago.

Activeupdated 4 days ago
argument-hint
[rebase|reorganization] [upstream=main] [Draft|Ready]

README badge

README badge for microsoft/nvx/nvx-rebase-openvmm-chain