Does this mean "render them nicely", or is this a very old ticket? because we technically show something now, although it's mostly useless.

I'm having some issues using the feed.http-hooks with the system I'm interacting with. My endpoint (trac) requires a CSRF token. I assume there aren't plans to add any sort of (even low-level support) for that? That's totally fine, this is kind of an edge case anyway.

I was able to reproduce on this install by passing rPf712ae718ccc1c94d882c626ca8626b77346026b to the Herald test console.

We're looking for a similar concept for Reviewers:
Even if the Author of a review is one of the Owners, we still want to automatically add that package.
This is mostly just T1125 - we want to make it easier to assign reviewers, and Owners has good UI for selecting paths.

Sorry for the late reply. What an incredibly well written and thoughtful response! Thanks!

Broadly, this isn't a use case we intend to support specifically. See T5873, T10363, T11330, T11563#192717 for some related discussion.

In T11530#192966, @chad wrote:

Maybe create a bot user called @shipit to trigger herald? Mentioning users CCs them to the object, but mentioning projects does nothing currently.

Maybe create a bot user called @shipit to trigger herald? Mentioning users CCs them to the object, but mentioning projects does nothing currently.

Herald firing on other things: T10109

Just reopening this so I don't forget about it since I agree about that last change.

Thanks for the report! This should be fixed in HEAD of master, and promote to stable in a few days. Let me know if I missed anything or you're seeing other issues.

I broke this in D16360, on August 1.

This has promoted to stable and doesn't seem like a contentious change so I don't currently anticipate any need to keep this open or revisit it.

Personal Herald rules do not run for disabled users, so disabling a user will disable all of their personal rules.

Thank you for exhaustive description. One more question:

You could also do this with no custom code by using Herald to trigger a Harbormaster build and having that make an HTTP request to something which runs the logic, or theoretically by using feed.http-hooks or Doorkeeper (although these are probably better after T10363).

Yay

Primarily, global rules bypass access control policies. They can also apply different actions.

Great and very helpful change, thank you!

T11428 puts the corporate communication wheels in motion to make this change.

Oh, I think I made up point (1) above -- that's already the behavior.

In T11312#188006, @Danny_B wrote:

there is no (preferably customizable) real feed (Atom, RSS). [...] there was some task here about it but I can't find it now.

A small (partially off-topic) note about feed - in such a high traffic Phabricator instance like ours (WMF), it is nearly unusable. Fortiori if there is no (preferably customizable) real feed (Atom, RSS). Lack of feed support in Phabricator is one of its biggest disadvantages. I know there was some task here about it but I can't find it now.

As I was asked to provide some input here:

In T11312#187893, @epriestley wrote:

• Why aren't they using "Send me an email" rules?

That is what I am currently doing via Herald in our Maniphest installation. :)

• Why aren't they using Feed?

As a bugmaster, my workflow is primarily email-based (describing a fact here that likely could be challenged). I receive notifications on Maniphest task changes which interest me and filter / process them. I abuse the "Unread" status of certain emails to mark stuff I'd like to follow up on later. I have not played with Feed (or an application to consume feeds) to be able to judge whether that would also suit my needs on processing large amounts of information and acting on some of that.

• Why do they want all of this information in the first place?

As a bugmaster, I'd like to get informed of most / nearly all changes on tasks, to allow me clarifying task descriptions (steps to reproduce etc), escalate issues that seem important, manage expectations, etc., to support our many stakeholders.

I'm going to close this in favor of T10448, which discusses fixing "other" tags and generally improving how tags work.

I think custom forms (today), workboard support for custom forms (likely, in the future), and T8442 are the most promising ways forward here.

It's still not really clear to me what this issue is describing. Here are my best guesses at how to fix various things which might be problems?

T7961 is probably worth fixing while I'm in here.

I'm going to at least fix the instanceof mess before adding a Calendar adapter in T7939.

I'm curious, is there any other way to trigger Herald to process a Differential review *other* than uploading a new diff?

Yes, nothing is in the transcript, in other words, no job was triggered

I won't comment on the specifics, but have you looked at the herald transcript? I normally find the answer hiding in there.

no.. they've been a part of that project since the beginning

If you're not allowed to see PHID-PROJ-rwnekrajar5m6diprobx, it will not be returned from project.query. Herald should be seeing all projects though, so PHID-PROJ-quo7cpreceuh6hnor3pw missing is strange.

yes... they're secret :)

Is there anything special about the projects PHID-PROJ-rwnekrajar5m6diprobx and PHID-PROJ-quo7cpreceuh6hnor3pw? Is any of them secret?

I think the root problem here is that "Herald added a subscriber: $user" is seen as email-spammy yet people are unwilling to edit their preferences to disable notifications for subscription-changes.