Refuse a shared file no consumer would keep #3
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/enforce-the-shared-layout-contract"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Consumers enumerate Renovate
fileFilters. A shared file outside that shape is written on the update branch, dropped before the commit, and leaves a lock describing content the branch does not have.Only this end can refuse the first such file: the consumers can check what is already in their lock, not what a future tag will add.