Page MenuHomePhabricator

Allow Herald text list fields to use "Exists" / "Does not exist" conditions
ClosedPublic

Authored by epriestley on Jun 21 2016, 4:21 PM.
Tags
None
Referenced Files
F18944700: D16158.diff
Nov 11 2025, 4:44 PM
F18903052: D16158.id38875.diff
Nov 8 2025, 3:47 AM
F18896228: D16158.id.diff
Nov 7 2025, 3:53 PM
F18795810: D16158.diff
Oct 17 2025, 2:30 AM
F18773445: D16158.id.diff
Oct 9 2025, 9:57 AM
F18751498: D16158.id38875.diff
Oct 4 2025, 11:24 AM
F18743693: D16158.id38871.diff
Oct 3 2025, 12:30 AM
F18695193: D16158.diff
Sep 27 2025, 5:14 AM
Subscribers
None

Details

Summary

This makes it more natural to write Herald rules about commits that appear on any or no branches.

Test Plan

Wrote a commit rule for commits on any branch, ran it with bin/repository reparse --herald <commit>, saw expected results in web UI.

Diff Detail

Repository
rP Phabricator
Branch
herald1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 12752
Build 16226: Run Core Tests
Build 16225: arc lint + arc unit

Event Timeline

epriestley retitled this revision from to Allow Herald text list fields to use "Exists" / "Does not exist" conditions.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.

The other field type which uses this is "Affected Files" (for commits and revisions).

(It probably isn't too useful there, but shouldn't hurt anything, and I suppose you could write a commits rule to forbid empty commits.)

chad edited edge metadata.
This revision is now accepted and ready to land.Jun 21 2016, 5:20 PM
This revision was automatically updated to reflect the committed changes.