Development record
When an app pushed the tip of a status branch, the forge's activity record never names that push, because the pusher check passes over app actors; so every status fetch asks the forge about that branch again and shows the line that the record does not yet name the tip.
issueresolvedminoriss-2610161928560772
When an app pushed the tip of a status branch, the forge's activity record never names that push, because the pusher check passes over app actors; so every status fetch asks the forge about that branch again and shows the line that the record does not yet name the tip.
Frontmatter
| id | iss-2610161928560772 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610161928560772-when-an-app-pushed-the-tip-of-a-status.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610171626391435The v0.15.1 release review found at CHANGELOG.md:54-56,61: Four Fixed lines are written as fixes to behaviour no earlier release had. 'A status fetch reads an app's push ... no longer asked about again' (iss-2610161928560772) concerns `abcd status`, which did not exist at v0.15.0. The three cloud lines ('no longer reported as started', 'no longer reports a refused commit', and the author identity line) concern scripts/cloud, which `git ls-tree v0.15.0 -- scripts/cloud` shows did not exist then either. A reader infers the features shipped earlier. The 'no longer' wording also contradicts the section's own preamb…