- User Since
- Aug 18 2022, 15:27 (58 w, 6 d)
Mon, Sep 25
Mon, Sep 18
PhabricatorFileAttachmentQuery seems to eagerly load the object relation, however since the DestructionEngine extensions run after the object is already deleted, this fails and nothing is returned in the query. Changed to LiskDAO loadAllWhere, which also seems to use less queries in general (due to not eagerly loading), so changed the query in PhabricatorFile as well. Changed mpull to foreach per suggestion.
Sun, Sep 17
Commit fixup/update author details
Organised attachment deletion from the file side into the File object and deletion from the object side into the destruction engine extension. Also updated the SQL patch date in the file name.
Apr 24 2023
There is no way to merge from the web UI.
(Ignored unrelated build failures, see fix: D25133)
Rebased and applied suggested changes
Apr 23 2023
Mar 27 2023
Mar 23 2023
Use project slug
Mar 22 2023
Mar 2 2023
Feb 21 2023
Rebased on master, ran bin/celerity map to resolve merge conflict.
Feb 20 2023
Feb 17 2023
Nov 29 2022
Yes, you could also use milestones and tag the task with that milestone. For example, this is done at Wikimedia's Phabricator: https://phabricator.wikimedia.org/project/subprojects/5539/, where milestones are used to track changes associated with a task.
Nov 28 2022
Nov 25 2022
Oct 16 2022
In addition to the above, it seems that commit d017f3f21021 is what broke this. And adjustTransactionValues is what changes the xaction from
Array ( [+] => Array (  => PHID-PIMG-m5pqg3eec46uvzw6uynm )
Oct 13 2022
Sep 28 2022
Sep 19 2022
Auto file attachments are also not working when editing a comment.
Differentiate between metadata of different text areas using node ID. e.g., new comment text areas and text areas in the edit comment dialog.
Sep 18 2022
ran celerity map again
Sep 12 2022