odoo-repo-map
Resolve an Odoo project to its git repo, base branch, Odoo series, and environment chain (dev → staging → production). Use before cutting a worktree, opening a PR, or planning a release, and when a project is added or renamed.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- odoo-repo-map
- description
- Resolve an Odoo project to its git repo, base branch, Odoo series, and environment chain (dev → staging → production). Use before cutting a worktree, opening a PR, or planning a release, and when a project is added or renamed.
- user-invocable
- false
02 资源文件 6
- 脚本scripts/project-bootstrap.sh4.4 KB
- 脚本scripts/project-resolve.sh5.5 KB
- 脚本scripts/repo-map.sh5.7 KB
- 脚本scripts/repos-dir.sh4.0 KB
- 脚本scripts/tests/repo-map.test.sh10.4 KB
- 脚本scripts/tests/repos-dir.test.sh6.0 KB
03 SKILL.md 正文
Odoo Repo Map
One answer to "this Odoo project: which repo, which branch, which series, what comes after this branch?". Nothing is inferred from a checkout: the GitHub default branch is not the base, the folder name is not the project name, and the chain lives nowhere in git.
The scripts here are thin wrappers over odoo-dev repo-map. The CLI validates, backs up
and writes the map.
The data
${ODOO_DEV_HOME:-$HOME/.config/odoo-dev}/repo-map.json. The devcontainer sets
ODOO_DEV_HOME. The first write creates the file. A map that does not parse exits 4 naming
the complaint. It is never reseeded.
The file holds defaults and one entry per exact Odoo project.project name:
| Key | Meaning |
|---|---|
repo |
A folder name under the repos tree, or an absolute path to the checkout |
odoo_version |
The series this project runs, e.g. 18.0 |
aliases |
Other project.project names that resolve to this entry. Never an entry name. Each alias appears once in the map |
branch_flow |
Ordered environment chain, e.g. ["task","UAT","main"]. Empty means defaults.branch_flow |
upgrade_branch |
Object of target series to branch, e.g. {"19.0":"19-upgrade"}. A series with no key uses the last element of the flow |
release_assignee |
GitHub login a release PR is assigned to. Empty means the default |
release_reviewer |
GitHub login the release PR requests review from, or none. Empty means the default |
defaults holds branch_flow (initially ["task","E2E","UAT","main"]), release_assignee
and release_reviewer. Change them with odoo-dev repo-map defaults.
Facts:
taskis only ever element 0 ofbranch_flow. It stands for the per-task branch.- The base branch of a task is the first element after
taskthat exists onorigin. A missing branch is skipped. - The last element of
branch_flowis production. - The keys of older maps that no longer exist are dropped by the reader. The default branch is derived from the flow, never stored.
- A
.odoo-repos-dirmarker file declares a repos tree that holds one clone. It outranks the two-git-subdirectories sweep.REPOS_DIRis the per-shell equivalent.
Scripts
Write every path in full.
| Script and arguments | Prints | Exit |
|---|---|---|
repos-dir.sh [--raw] |
{"repos_dir"} from $REPOS_DIR, then the marker, then the sweep |
0 · 1 no tree (an absolute repo skips it) |
repo-map.sh get "<name>" | list | validate | remove "<name>" [--json] |
the CLI output of the same verb | 0 · 2 usage · 3 unmapped · 4 map invalid |
repo-map.sh add "<name>" <repo> --odoo-version V [--aliases A,B] [--branch-flow task,UAT,main] [--upgrade-branch 19.0=BRANCH]... [--release-assignee X] [--release-reviewer Y] |
odoo-dev repo-map set |
0 · 2 usage or already mapped · 4 invalid |
repo-map.sh set "<name>" [--repo R] [--odoo-version V] [same fields] |
odoo-dev repo-map set, keeping every field not named |
0 · 2 · 3 · 4 |
repo-map.sh set-flow "<name>" "task,UAT,main" |
set with --branch-flow. --flow-confirmed is accepted and ignored |
0 · 2 · 3 · 4 |
repo-map.sh set-release-owners "<name>" <assignee> <reviewer|none> |
set with the two logins |
0 · 2 · 3 · 4 |
project-resolve.sh "<project|alias|repo>" [--next-after <branch>] [--series NN.0] |
{"project","repo","repo_root","origin","odoo_version","branch_flow","base_branch","upgrade_branch","next_env","at_production","release_assignee","release_reviewer"} |
0 · 2 usage or a --series that is not NN.0 · 3 unmapped · 4 --next-after names a branch not in the flow · 6 ambiguous |
project-bootstrap.sh "<checkout path>" [--project NAME] |
the entry it wrote, as JSON | 0 · 2 not a git checkout or no series found · 3 already mapped (entry printed) |
JSON helper: plugins/odoo-dev/scripts/json-get.sh '<expression on d>' reads JSON on stdin.
Use it to read one field from any output above.
Resolve
<base directory>/scripts/project-resolve.sh "B&K Logistics Support"
<base directory>/scripts/project-resolve.sh "B&K Logistics Support" --next-after task # -> next_env: "UAT"
--next-after takes an element of the chain. The first hop is --next-after task. repo_root
and base_branch are null when no checkout is on this machine. branch_flow is the
effective flow (the entry's own, else the defaults). The two release_* fields fall back to the
defaults and are null when neither is set.
exit 3— unmapped → runproject-bootstrap.sh "<checkout>", then resolve again by the project name it printed; still 3 → stop, report the path and the output.exit 4— the branch is not in the flow → stop; report the flow.exit 6— ambiguous: one repo folder maps to several projects → stop; list the candidate project names; never pick one.exit 2— usage → fix the call.
Bootstrap an unmapped checkout
<base directory>/scripts/project-bootstrap.sh /mnt/extra-addons --project "ACME Support"
It records repo and odoo_version from the checkout. The flow is left empty, so the entry
uses the defaults. repo is the folder name when the repos tree holds it, else the absolute
path.
exit 3— this checkout is already mapped by the printed entry → resolve by that project name; never add a second entry.
Edit
<base directory>/scripts/repo-map.sh add "New Client - Phase 1" newclient \
--odoo-version 18.0 --branch-flow "task,UAT,main" \
--release-assignee alice --release-reviewer bob
<base directory>/scripts/repo-map.sh set "New Client - Phase 1" --odoo-version 19.0
<base directory>/scripts/repo-map.sh set "New Client - Phase 1" --aliases "New Client - Support,New Client - Care" # "" removes them
<base directory>/scripts/repo-map.sh set "New Client - Phase 1" --upgrade-branch 19.0=19-upgrade # repeatable; 19.0= removes that series
<base directory>/scripts/repo-map.sh set-flow "New Client - Phase 1" "task,UAT,main"
<base directory>/scripts/repo-map.sh set-release-owners "New Client - Phase 1" alice bob
<base directory>/scripts/repo-map.sh add "Client - Support" /mnt/extra-addons --odoo-version 18.0
addonly creates and refuses a duplicate. It does not check that the repo folder exists.setkeeps the fields you do not name.- Never
removethen re-addto change a field. - One entry per customer repo. A second Odoo project on the same repo and chain is an
alias, not an entry.
set,set-flow,set-release-ownersandremovetake the entry name or, forset*, an alias. - The CLI writes atomically and keeps one
.bak.
Rules
- An unknown project is a stop, never a guess. Bootstrap first, then stop on what remains.
- An entry is added only with explicit user confirmation of repo, series and chain.
- One repo with several projects is normal. Those entries can disagree on
odoo_versionandbranch_flow. Name the project. - Never hand-edit the map file.
base_branchis what a task PR targets. It is often not the GitHub default branch.
04 同仓库更多 Skills
report-incident
Draft a terse GitHub issue for an incident in the Odoo dev suite (odoo-dev, odoo-orchestrator, dispatcher), with a current environment block and no private data. Files it only after you approve. Use when a tool or workflow failed.
principles
Engineering principles indexed as one-liners: safety and correctness, design and architecture, composition and interfaces, code structure, performance, visibility. Use when writing new code, reviewing a diff, or justifying a design choice.
odoo-upgrade
Plan and run code upgrades of custom Odoo modules between major versions (16.0→17.0→18.0→19.0). Use to migrate or port a module or addon, for breaking changes, a module inventory, or an upgrade estimate or plan.
odoo-upgrade-project
Human SOP for a whole Odoo upgrade project past the code port: staging database upgrade through upgrade.odoo.com, on-prem restore, cutover, go-live, support tickets and functional requirements. A planning reference.
odoo-test-run
Run an Odoo module's unit tests and HttpCase browser tours on a throwaway database and return machine-checkable evidence: tests executed, tours executed, failure lines. Use before a PR, after a fix, or when a green run never said how many tests ran.
odoo-task-env
Stand up the working environment for one Odoo task: find work that already exists, create or reuse an isolated git worktree on the task branch, bring a runnable stack up. Use at the START of implementing any task, and whenever one is picked back up.