This makes it more natural to write Herald rules about commits that appear on any or no branches.
Details
Details
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
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
Comment Actions
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.)