Page MenuHomePhabricator

Give "x committed <commit>" feed stories an explicitly higher action strength than other transactions
ClosedPublic

Authored by epriestley on Jun 8 2017, 12:45 PM.
Tags
None
Referenced Files
F18791471: D18104.diff
Thu, Oct 16, 1:50 PM
F18782559: D18104.id43551.diff
Mon, Oct 13, 1:59 AM
F18764637: D18104.diff
Tue, Oct 7, 6:59 AM
F18674302: D18104.diff
Thu, Sep 25, 2:12 PM
F18642355: D18104.diff
Sep 18 2025, 11:40 PM
F18629762: D18104.diff
Sep 16 2025, 9:50 AM
F18629367: D18104.id43551.diff
Sep 16 2025, 8:37 AM
F18597752: D18104.diff
Sep 13 2025, 3:34 AM
Subscribers
None

Details

Summary

Fixes T12811. The issue here appears to be that both the "alice committed rXYZabc" and "Herald added projects..." actions have the same (default) strength and end up applying in arbitrary order, and probably got shuffled around as this transitioned to Modular transactions.

Give "alice committed rXYZabc" an explicitly higher action strength.

Test Plan
  • Wrote an "Always, add project X" Herald rule for commits.
  • Ran bin/repository reparse --herald ....
  • Saw an "alice committed rXYZabc" story instead of a "Herald added projects: X" story.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable