Change Details

Currently we would like to implement a policy where concerns raised during audit result in tasks created for that developer in Maniphest. This takes a lot of time and we'd like to automate it. We tried Herald, but it does not have any triggers for raised concerns. An ideal result would be that a Maniphest task is created and assigned to the user who made the problematic commit once and only once per commit. The commit would be attached to the task (and the task would be attached to the commit) and the task would be named along the lines of "Address raised concerns in commit Rxxxxx". The task description could be left blank or could contain a count or summary of raised concerns from the commit.

We would like to get a history of commits that were made in order to fix a concern raised against a commit during Audit because this makes it easier for reviewers to follow up on changes made post-audit without the committer having to remember to CC the auditors in every commit. This is currently possible manually by creating a Maniphest task, attaching the concerning commit to the task, and then referencing that Maniphest task in all new commits made to fix the concerning commit. The task history then represents a history of actions taken to fix a failed Audit which auditors can comment on in context. Since the task must always be made after the failed Audit and then attached, this process cannot be sped up via commit message triggers and since Herald does not allow triggering on raised concerns, this cannot be automated currently.

Currently we would like to implement a policy where concerns raised during audit result in tasks created for that developer in ManiphesWe would like to get a history of commits that were made in order to fix a concern raised against a commit during Audit because this makes it easier for reviewers to follow up on changes made post-audit without the committer having to remember to CC the auditors in every commit. This takes a lot of time and we'd like to automate it.is currently possible manually by creating a Maniphest task, attaching the concerning commit to the task, We tried Herald,and then referencing that Maniphest task in all new commits made to fix the concerning commit. but it does not have any triggers for raised concernsThe task history then represents a history of actions taken to fix a failed Audit which auditors can comment on in context. An ideal result would be that a Maniphest task is created and assigned to the user who made the problematic commit once and only once per commit.Since the task must always be made after the failed Audit and then attached, The commit would be attached to the task (and the task would be attached to the commit) and the task would be named along the lines of "Address raised concerns in commit Rxxxxx".this process cannot be sped up via commit message triggers and since Herald does not allow triggering on raised concerns, The task description could be left blank or could contain a count or summary of raised concerns from the committhis cannot be automated currently.