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
F19464886: D18104.id.diff
Sat, Jan 3, 2:30 AM
F19275805: D18104.id43561.diff
Tue, Dec 23, 12:54 AM
F18855334: D18104.id.diff
Nov 1 2025, 4:55 AM
F18835792: D18104.diff
Oct 26 2025, 6:41 PM
F18835583: D18104.id43551.diff
Oct 26 2025, 5:05 PM
F18791471: D18104.diff
Oct 16 2025, 1:50 PM
F18782559: D18104.id43551.diff
Oct 13 2025, 1:59 AM
F18764637: D18104.diff
Oct 7 2025, 6:59 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