Stop an unscoped deploy from rebuilding the whole repository
bin/build asks the local repository database which packages are already built. A build machine has no such database, so every package looks out of date: an unscoped 'bin/repo deploy' on this laptop would have built all 108 packages and published them. Verified with a dry run. deploy now refuses to run unscoped when that database is absent, and push refuses the same combination under --yes, where nobody would see the list it prints before publishing. Both are allowed on the repository host, which has the database that makes the comparison meaningful. Also states the split in the README: build, push and deploy are the three commands that may run off the repository host; everything else works on the published tree directly. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
736579a6eb
commit
51004999e7
4 files changed
+59
No files matched your search
@@ -33,6 +33,16 @@ resolve_repo_host() {
|
||||
return 1
|
||||
}
|
||||
|
||||
# True when this checkout holds the published repository, which in practice means
|
||||
# this machine is the repository host. Every other command in bin/ works on that
|
||||
# tree directly; build, push and deploy are the ones that may run elsewhere.
|
||||
#
|
||||
# The database is the marker rather than the directory: bin/build creates empty
|
||||
# mirror directories as a side effect, so their presence proves nothing.
|
||||
on_repo_host() {
|
||||
[[ -f "$REPO_DIR/omarchy.db" || -f "$REPO_DIR/omarchy.db.tar.zst" ]]
|
||||
}
|
||||
|
||||
# Shared wording so every command explains configuration the same way.
|
||||
print_no_repo_host() {
|
||||
print_error "No repository host configured"
|
||||
|
||||
Reference in new issue
Block a user