635ae452f1d0a563c2d5c055bce8614eb2cefdf6
The release commit lands on main, because tools/release.sh refuses to run anywhere else, while the working branch keeps advancing. So after every release neither tip is an ancestor of the other and --ff-only fails in both directions -- a refusal that reads as "the tree is not ready" when the tree is fine. It cost confusion on both v1.38.0 and v1.40.0, and both times the correct answer had to be re-derived from the commit graph. Documents the order that keeps a conflict off main (merge main into the branch first, then fast-forward), and the trap that catches people looking for main: a detached worktree sitting at the same commit accepts --ff-only and moves nothing, which looks like success.
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
132 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.7%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%