D20427 is a similar change, that deprecates the "Commit is on autoclose branch" field. This fields is now always true by definition, because Herald does not run until a commit is reachable from a permanent ref (previously called an "autoclose branch").
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 22 2019
Apr 16 2019
Apr 15 2019
This is effectively mooted by changes in T13277.
I think this is effectively resolved by T13277.
Apr 14 2019
Apr 11 2019
Apr 10 2019
Internally, see PHI1165 for nine pages of me complaining about this.
Apr 2 2019
Jan 23 2019
I think this is more or less at the end of the line in terms of actionable work that doesn't make more sense being scoped in elsewhere.
Jan 21 2019
Jan 17 2019
Jan 16 2019
Jan 14 2019
Currently, the SES adapter extends from the Sendmail (PHPMailerLite) adapter. I'd like to fix this.
Jan 5 2019
Currently, the SES adapter extends from the Sendmail (PHPMailerLite) adapter. I'd like to fix this.
Jan 4 2019
Jan 3 2019
Jan 2 2019
As tends to be par for the course, this is turning into a bit of a rabbit hole.
Dec 30 2018
I'm considering pushing this forward since MFA is getting an update (see T13231 and adjacent tasks).
Sep 10 2018
Aug 30 2018
With D11419 implemented, is it possible to now allow Herald rules to be triggered on a cron (even a very simple 'daily' option would be good)?
Aug 13 2018
Aug 2 2018
On SMS MFA, Reddit got bitten recently by SMS having poor security properties:
Jul 17 2018
I'm going to look at improving the push logs a bit to show which rule blocked a push to address the actual use case in PHI765, which makes this more of a distance nice-to-have.
Jul 16 2018
I think the following change to src/applications/herald/controller/HeraldRuleController.php line 672 (as of 185c28f307e4) should provide an immediate improvement to at least indicate that they are different rules:
Apr 25 2018
See PHI612 and elsewhere; using "Take action [the first time this rule matches]" isn't always obvious but is usually a better fit than "When [ thing is created ]" and interacts much better with drafts.
Mar 29 2018
Feb 27 2018
Okay. For the sake of 100% clarity it would be nice if the timeline story did show why the action was taken as it isn't immediately clear (unless you've read the documentation of course) why it was removed.
Feb 26 2018
I'll make a note on T12455, but we might be able to render this timeline story more clearly, e.g. "X added project Y (which automatically removed Z, a subproject)" but I think this is likely fairly natural/obvious in most cases and I'm not sure if it's trivial to completely explain in the timeline.
Ah, that would certainly explain it. Sorry for the noise - when entering this I did wonder if I had missed something as it didn't make sense that a name collision would be able to cause this.
"Plasma on Wayland" is a subproject of "Plasma".
Feb 12 2018
Sorry, the only way to influence feature development is through a support pact. See also Planning.
@epriestley Would you guys be open for a patch for this? How would you like to see this implemented in order to be acceptable for you guys?
Feb 10 2018
Feb 9 2018
Feb 8 2018
Feb 5 2018
Jan 29 2018
Jan 26 2018
This is quite old and I have no idea how to reproduce it and thus no idea how to fix it. Locally, I tried a few things and wasn't able to identify a case where the Herald field value differed from my actual project list.
Jan 25 2018
Rename the field to "Reviewer (Legacy)", or move it to a "Legacy" category -- maybe improves things, but really just punts this.