A deployment run as a fork will sometimes fix something in production first, because production is what is broken. Those fixes are easy to forget, and a forgotten one is how the two copies quietly diverge. Commits carry an 'Upstream: yes' or 'Upstream: no — reason' trailer, and `make upstream-pending` lists both what is marked and still owed, and what carries no marker at all so the decision is visible rather than skipped. Upstream: no — this is tooling for forks, but it belongs in the shared Makefile so every deployment gets it rather than reinventing the wrapper.main
parent
5093bda314
commit
bc9f2efaa8
1 changed files with 13 additions and 1 deletions
Loading…
Reference in new issue