You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Patch files can be read at a git ref — a tag, branch or SHA — instead
of the working tree: ref on MCP's apply_patches and pending_patches, pgman apply --ref. The ref is resolved once to a
commit, named in the plan, the confirmation, the result and the audit
log line, and read through git ls-tree / git cat-file; nothing is
checked out.
A plan or pending_patches read from a git checkout's working tree
warns about what differs from its commit: patch files not committed
or changed since, a branch other than the default, commits behind its
upstream (as of the last fetch), and a remote database.
pending_patches without a [patches] block takes the settings from
an environments.tomlversion_table whose patches directory is
inside the project, when all such agree; a missing setting's error
names every missing one and a block to paste.
Changed
MCP apply_patches refuses a remote database's patches from a
checkout's working tree without ref; a local database, or a patches
directory outside git, is as before. An apply at the same ref as the
session's dry run that finds another commit is refused. Any other run
after a dry run that reads another commit (another spelling of the
ref, another ref, the working tree) opens its confirmation by saying
so.
apply_patches' confirmation names where the files came from: the
ref and its commit, or the checkout's working tree with its branch
and commit. A protected environment over loopback warns that its
files aren't a named commit.
A patch plan reads every file once, before connecting, and runs the
texts it read. A patch file over 16 MB is refused by its size, where pending_patches used to read only its first 1 MB.
Security
git, wherever pgman runs it in a checkout, ignores replace refs (which
could make a named commit yield another commit's files) and fetches
nothing: a partial clone's missing object reads as missing, rather
than being fetched through the remote's transport from the checkout's
config (core.sshCommand, a credential helper).