Request: delete closed PRs #541 and #542 (contain internal infrastructure identifiers)

[beipang]

Hi team,

I accidentally opened two PRs against this upstream repo instead of my fork. (😮‍💨 default github UI)

Both are already closed, but the commits contain internal Databricks workspace URLs and warehouse identifiers that shouldn't be in a public repo.

Could a maintainer delete both PRs so GitHub's GC can eventually collect the unreferenced commits?

• Bei/poc noom mcp monkey patch #541 (Bei/poc noom mcp monkey patch)
• Add noom-mcp-server: monkey-patch extension layer for SQL governance #542 (Add noom-mcp-server)

Thanks

[calreynolds]

Hi @beipang — thanks for flagging. Quick clarification on what we can do from this side: GitHub doesn't let repo admins (or anyone
outside GitHub Support) delete a PR, and closing one doesn't unreference the commits because GitHub's fork-network caches them as
accessible via the …/pull/N/commits URLs.

The commits and the leaked identifiers actually live in your fork and Noom's fork, not in this repo, so the most effective action
is on your end:

For #541 — please delete the branch bei/poc_noom_mcp_monkey_patch from beipang/poc-forked-ai-dev-kit (commit a454e160).
If you can delete the fork entirely, even better — that removes the last ref keeping those commits reachable.

For #542 — this one is on noom/databricks-ai-dev-kit (branch noom-mcp-server, commit eef1ebd5), so someone with admin on
that Noom-org fork needs to delete the branch / fork.

We'll then be able to remove this PR 👍

Also worth treating any credentials adjacent to the leaked workspace URL / warehouse IDs as compromised and rotating, just to be
safe.

[beipang]

Hi @calreynolds !

I just removed the fork beipang/poc-forked-ai-dev-kit and branch noom-mcp-server

Thank you for your patience and help!