bmsdna-devtools 0.2.0__py3-none-any.whl

bmsdna/devtools/skills/bmsdna-devtools/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: bmsdna-devtools
+description: >
+  Use the `bdt` CLI (from the bmsdna-devtools package) instead of ad hoc git/az/gh
+  commands or repo-local scripts for: checking PR build/check status, creating
+  a PR, creating a git worktree, committing and pushing files (with pre-flight
+  checks), and querying Azure logs. `bdt pr *` works against both Azure DevOps
+  and GitHub — it auto-detects which one from the `origin` remote. Trigger
+  whenever the user asks to check a build/PR status, create a PR, make a
+  worktree, commit changes, or fetch/tail application logs in a repo that has
+  bmsdna-devtools installed (check for `bdt` on PATH, or `bmsdna-devtools` in
+  pyproject.toml, before assuming it applies).
+---
+
+# bmsdna-devtools — shared BMS developer tooling
+
+A single `bdt` CLI replacing the near-duplicate `get_pr_build.py`,
+`commit.py`, and `just worktree`/`just pr-main` recipes that used to be
+copy-pasted across OneSales, ccmt2, and MDMApp. Install with
+`uv tool install bmsdna-devtools` (global) or `uv add bmsdna-devtools`
+(per-project).
+
+`bdt pr *` auto-detects Azure DevOps vs. GitHub from the `origin` remote and
+shells out to `az`/`gh` accordingly — you don't need to pick a backend
+yourself, and there's no need to fall back to raw `gh pr create`/`gh pr
+checks` for a GitHub-hosted repo, `bdt pr *` covers that too. Each external
+CLI (`az`, `gh`) is only required for the commands that actually need it,
+and is checked lazily with a clear "not found, install it here" error
+rather than a raw traceback — if you see that error, tell the user which
+CLI to install rather than trying to work around it.
+
+## Checking PR build/check status
+
+```bash
+bdt pr status [--target-branch main] [--wait]
+```
+
+Finds the PR opened from the current branch and prints build/check status,
+inlining failed-step logs. `--wait` polls until everything finishes (use
+this after pushing, instead of guessing when CI is done). Exits non-zero if
+anything failed — safe to gate a script on. If the PR has merge conflicts
+(or, on Azure DevOps, failed/was rejected by policy), that's reported
+immediately instead of waiting for builds that will never run — check the
+error message for `mergeStatus=conflicts` (ADO) or `mergeable=CONFLICTING`
+(GitHub) and tell the user to resolve conflicts rather than assuming CI is
+just slow.
+
+`--target-branch` only applies on Azure DevOps (its search API needs one to
+find the right PR); on GitHub, `gh pr view` always resolves the PR for the
+current branch regardless, so the flag is ignored there — the PR's actual
+base branch is shown in the output instead.
+
+Auth: Azure DevOps works with no setup if the caller is already `az
+login`'d (only pass `--pat`/`AZURE_DEVOPS_PAT` if there's no `az` session
+available); GitHub uses whatever `gh auth login` session is active.
+
+## Creating a PR
+
+```bash
+bdt pr create --target main    # or --target test
+```
+
+Uses the current branch as source. On Azure DevOps this wraps `az repos pr
+create`; on GitHub, `gh pr create --fill` (autofills title/body from commit
+info, so it never blocks waiting on an interactive prompt). Extra args pass
+straight through either way, e.g.
+`bdt pr create --target main -- --title "..." --description "..."`.
+
+## Creating a worktree
+
+```bash
+bdt worktree <name> [--base dev] [--install "just install"]
+```
+
+Creates `.worktrees/<name>`, inits submodules if `.gitmodules` exists,
+copies an env file in (auto-detects `.local_env` then `.env`), and runs
+`--install` inside the new worktree if given. Prefer this over raw
+`git worktree add` so env-file copying and submodule init aren't forgotten.
+
+## Committing and pushing
+
+```bash
+bdt commit "feat(x): add widget support" file1.py file2.py
+```
+
+Use this instead of raw `git commit && git push` in any repo where it's
+the established convention (check the repo's AGENTS.md/CLAUDE.md — several
+BMS repos mandate it). It runs pre-flight checks (files exist, message
+looks like `type: description`, not on `main`/`master`) and retries once
+if a pre-commit hook reformats files. Pass `--json` when calling
+programmatically from an agent loop — the schema is documented in
+`bdt commit --help`. Pass `--subrepo database` (repeatable) for repos that
+vendor a git submodule under that path.
+
+## Application Insights logs
+
+```bash
+bdt logs roles --resource-group <rg> --app-insights <name> --minutes 60
+bdt logs tail --resource-group <rg> --app-insights <name> --role <role> --level warning
+```
+
+`logs roles` lists which `cloud_RoleName`s have recent traffic — run this
+first if you don't already know the role name to filter `logs tail` by.
+No defaults are baked in (unlike the other commands, this can't infer
+anything from the git remote) — always pass `--resource-group`/`--app-insights`
+or set `AZURE_RESOURCE_GROUP`/`AZURE_APP_INSIGHTS`.
+
+For "what broke recently" without a KQL query, `bdt logs fetch --webapp
+<name> --resource-group <rg> --slot <slot>` downloads the App Service log
+archive and extracts error/warning lines to `logs/<slot>_errors.log` —
+often the faster path when you don't need a filterable trace stream.

bmsdna/devtools/worktree.py

@@ -0,0 +1,49 @@
+"""Create a git worktree for a new branch, mirroring the `just worktree` recipes."""
+
+from __future__ import annotations
+
+import shutil
+import subprocess
+import sys
+from pathlib import Path
+
+
+def _run(cmd: list[str], cwd: Path) -> None:
+    try:
+        subprocess.run(cmd, cwd=cwd, check=True)
+    except FileNotFoundError:
+        sys.exit(f"'{cmd[0]}' is required for this command but wasn't found on PATH.")
+
+
+def create(
+    name: str,
+    base: str = "dev",
+    env_file: str | None = None,
+    submodules: bool = True,
+    install_cmd: list[str] | None = None,
+    root: Path | None = None,
+) -> Path:
+    root = root or Path.cwd()
+    path = root / ".worktrees" / name
+    if path.exists():
+        sys.exit(f"error: {path} already exists")
+
+    _run(["git", "worktree", "add", str(path), "-b", name, base], cwd=root)
+
+    if submodules and (root / ".gitmodules").exists():
+        _run(["git", "submodule", "update", "--init"], cwd=path)
+
+    if env_file is None:
+        for candidate in (".local_env", ".env"):
+            if (root / candidate).exists():
+                env_file = candidate
+                break
+
+    if env_file and (root / env_file).exists():
+        shutil.copy(root / env_file, path / ".env")
+
+    if install_cmd:
+        _run(install_cmd, cwd=path)
+
+    print(f"worktree ready at {path}")
+    return path

bmsdna_devtools-0.2.0.dist-info/METADATA

@@ -0,0 +1,143 @@
+Metadata-Version: 2.4
+Name: bmsdna-devtools
+Version: 0.2.0
+Summary: Shared Azure DevOps / GitHub / git / Azure Monitor developer tooling for BMS projects
+Requires-Python: >=3.11
+Requires-Dist: requests>=2.32.0
+Requires-Dist: rich>=13.0.0
+Requires-Dist: typer>=0.26.7
+Description-Content-Type: text/markdown
+
+# bmsdna-devtools
+
+Shared developer tooling for BMS projects: PR build/check status, PR
+creation, git worktrees, a commit-and-push helper with pre-flight checks,
+and Azure log queries. `bdt pr *` auto-detects whether the current repo's
+`origin` remote is Azure DevOps or GitHub and uses `az`/`gh` accordingly.
+Consolidates near-duplicate scripts that used to be copy-pasted across
+OneSales, ccmt2, and MDMApp into one versioned package with a `bdt` CLI.
+
+Requires `git` always, plus `az` (Azure DevOps commands, and all `bdt logs`
+commands) and/or `gh` (GitHub commands) on PATH as needed — each is checked
+lazily, only when a command actually needs it, with a clear error and an
+install link if missing rather than a raw traceback. Works on Windows: CLI
+shims (e.g. `az.cmd`) are resolved via `shutil.which` (which honors
+`PATHEXT`) rather than shelling out, output is decoded as UTF-8 rather than
+relying on the console's default codepage, and file arguments accept either
+slash style.
+
+## Install
+
+```bash
+uv tool install bmsdna-devtools
+```
+
+Or as a project dependency: `uv add bmsdna-devtools`.
+
+## `bdt pr status`
+
+Find the PR opened from the current branch and report build/check status
+(failed steps print their logs inline). Works against Azure DevOps or
+GitHub — whichever `origin` points at.
+
+```bash
+bdt pr status [--target-branch main] [--wait]
+```
+
+If the PR can't be merged, that's reported immediately instead of polling
+for builds/checks that will never run — e.g. on Azure DevOps:
+`PR #42 ('feat: widgets') has merge conflicts with the target branch (mergeStatus=conflicts)`;
+on GitHub: `PR #42 ('feat: widgets') has merge conflicts with 'main' (mergeable=CONFLICTING)`.
+Exit code 1 either way.
+
+**Azure DevOps**: org/project/repo are auto-detected from
+`git remote get-url origin` (handles SSH, `dev.azure.com` HTTPS, and
+`*.visualstudio.com` HTTPS forms). Auth is an explicit PAT (`--pat` or
+`AZURE_DEVOPS_PAT` env var), falling back to a short-lived token from the
+caller's own `az login` — never embed a PAT literal in a script or CI file.
+`--target-branch` selects which PR to look at (ADO's search API needs one).
+
+**GitHub**: uses `gh`'s own auth (`gh auth login`) and always resolves the
+PR opened from the current branch — `gh pr view` has no target-branch
+filter, so `--target-branch` is ignored here; the PR's actual base branch
+is shown in the output. Check status is computed from
+`gh pr view --json statusCheckRollup` rather than `gh pr checks --json`,
+since the latter flag isn't available in all `gh` releases.
+
+## `bdt pr create`
+
+```bash
+bdt pr create --target main   # or --target test
+```
+
+Creates a PR from the current branch into `--target`. On Azure DevOps,
+a thin wrapper around `az repos pr create` (org/project/repo inferred by
+`az` itself from the git remote). On GitHub, `gh pr create --fill` (autofills
+title/body from commit info so it never blocks on an interactive prompt).
+Extra arguments pass through either way, e.g.
+`bdt pr create --target main -- --title "..."`.
+
+## `bdt worktree`
+
+```bash
+bdt worktree my-feature [--base dev] [--env-file .local_env] [--no-submodules] [--install "just install"]
+```
+
+Creates `.worktrees/<name>` branched from `--base`, initializes submodules
+(unless `--no-submodules`), and copies an env file into the new worktree as
+`.env` (auto-detects `.local_env` then `.env` if `--env-file` isn't given).
+
+## `bdt commit`
+
+```bash
+bdt commit "feat(x): add widget support" file1.py file2.py [--json] [--no-verify] [--subrepo database]
+```
+
+Stages, commits, and pushes the given files. Pre-flight checks: files
+exist, commit message looks like `type: description` (skip with
+`--skip-message-check`), not on `main`/`master` (skip with `--allow-main`).
+Retries once (re-`git add`) if a pre-commit hook reformats files. Pass
+`--subrepo <dir>` (repeatable) for repos that vendor a submodule (e.g.
+`database`) — files under that prefix are committed/pushed inside the
+submodule first, then the bump is staged in the parent repo.
+
+Set `IS_BMS_AI_SANDBOX=1` to skip the push step (commit only) — used when
+an AI coding sandbox pushes on its own schedule separately.
+
+`--json` emits a machine-readable result for AI-agent callers:
+
+```json
+{
+  "success": true, "committed": true, "pushed": true,
+  "message": "...", "files": ["..."], "commit_sha": "abc1234",
+  "error": null, "hint": null
+}
+```
+
+## `bdt logs roles` / `bdt logs tail`
+
+Query Application Insights (KQL over `traces`/`exceptions`) via
+`az monitor app-insights query`. No defaults are baked in — pass
+`--resource-group`/`--app-insights` explicitly (or set
+`AZURE_RESOURCE_GROUP`/`AZURE_APP_INSIGHTS`), since which Azure resource
+"this repo" maps to isn't derivable from the git remote.
+
+```bash
+bdt logs roles --resource-group my-rg --app-insights my-app-insights --minutes 60
+bdt logs tail --resource-group my-rg --app-insights my-app-insights --role my-service --level warning
+```
+
+## `bdt logs fetch`
+
+Downloads the App Service log archive for a webapp/slot via
+`az webapp log download`, unzips it, and writes every line matching a
+common error/warning marker (`ERROR`, `CRITICAL`, `WARNING`, tracebacks,
+`4xx`/`5xx`, `FAILED`, `FATAL`) to `<out>/<slot>_errors.log`. Simpler and
+often preferable to the KQL commands above when you just want "what broke
+recently" rather than a queryable trace stream — no defaults are baked in
+here either.
+
+```bash
+bdt logs fetch --webapp my-webapp --resource-group my-rg --slot production
+bdt logs fetch --webapp my-webapp --resource-group my-rg --slot production --out logs/ --keep-archive
+```

bmsdna_devtools-0.2.0.dist-info/RECORD

@@ -0,0 +1,17 @@
+bmsdna/devtools/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+bmsdna/devtools/ado_auth.py,sha256=w2CQx6Rz8YaDpRhGn_qi0YJw7w8KHqo6HnXz1DBKIYg,1269
+bmsdna/devtools/app_service_logs.py,sha256=hbF8Rc7oA7IEXDCJ6I6E_cGmiGPtqv4kLL2sVazbrWE,2475
+bmsdna/devtools/cli.py,sha256=38tKLcy-yNVQksK64oyRQ25iGgZ6YpyWkSHp_fvscOQ,6489
+bmsdna/devtools/cli_tools.py,sha256=uGvVUiIPKt0YUvvH8Sz-4SHgzz_g8tmO-poGZk5QTEg,1047
+bmsdna/devtools/commit.py,sha256=1AtqNPApOQ0F3Ani9LdVpRVXGGpYYV1r-BlKfcqdfxY,7843
+bmsdna/devtools/env_config.py,sha256=QpAkwRsdrPqEP7YQHlxLDVHmhbDmw0spSDnB-Xsagsk,1900
+bmsdna/devtools/gh_pr.py,sha256=TXb0ZHb5ZEp6LH91_n8cb90xBc5KVGLZJvhJh3ZnIXo,4657
+bmsdna/devtools/gitrepo.py,sha256=EbcCLjkAslAnk8ofJB3uh2Gv4MlxRxF7D0g6N0o10Vs,3920
+bmsdna/devtools/logs.py,sha256=sNKqMF4XcvydMHheRcsLJkRemNBqey7NskljzVcKorY,6393
+bmsdna/devtools/pr_build.py,sha256=EJxwc88sf0Y7Qg44QQo80VX0IZaGCETHs_EFxcTaE-I,7995
+bmsdna/devtools/worktree.py,sha256=mbfmnFtTleidAO4hiPGJ9zJpbfsvLL1qZsvYfpwBmmU,1339
+bmsdna/devtools/skills/bmsdna-devtools/SKILL.md,sha256=fe_IQAe8TLJS1ok6mInV0GW_L9Fyr1EvJl6f0ZApnYg,5094
+bmsdna_devtools-0.2.0.dist-info/METADATA,sha256=ETnKRPD80VqDhPCRsffmD7tuk17qRgLvWLHyvRzfehU,5891
+bmsdna_devtools-0.2.0.dist-info/WHEEL,sha256=lCkmxWfQsSc9CfIClYeavTdQeEX2toPqufh9gI35EQA,87
+bmsdna_devtools-0.2.0.dist-info/entry_points.txt,sha256=DdDUJbHPaZAI5u2kQoCXyn649vAzMLPhiTvUv-CcPNU,48
+bmsdna_devtools-0.2.0.dist-info/RECORD,,

bmsdna_devtools-0.2.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.31.0
+Root-Is-Purelib: true
+Tag: py3-none-any

bmsdna_devtools-0.2.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+bdt = bmsdna.devtools.cli:app