phacility/phabricator · warning · Exception

You can not raise a concern with this commit because you are

Error message

You can not raise a concern with this commit because you are the commit author. You can only raise concerns with commits you did not author.

What it means

DiffusionCommitConcernTransaction::validateAction() always forbids raising a concern on your own commit - unlike accept, there is no config override. The rule keeps audit pressure independent: concerns must come from someone other than the author.

Source

Thrown at src/applications/diffusion/xaction/DiffusionCommitConcernTransaction.php:47

  public function getActionName() {
    return pht('Raised Concern');
  }

  public function applyInternalEffects($object, $value) {
    // NOTE: We force the commit directly into "Concern Raised" so that we
    // override a possible "Needs Verification" state.
    $object->setAuditStatus(DiffusionCommitAuditStatus::CONCERN_RAISED);
  }

  public function applyExternalEffects($object, $value) {
    $status = PhabricatorAuditRequestStatus::CONCERNED;
    $actor = $this->getActor();
    $this->applyAuditorEffect($object, $actor, $value, $status);
  }

  protected function validateAction($object, PhabricatorUser $viewer) {
    if ($this->isViewerCommitAuthor($object, $viewer)) {
      throw new Exception(
        pht(
          'You can not raise a concern with this commit because you are '.
          'the commit author. You can only raise concerns with commits '.
          'you did not author.'));
    }

    // Even if you've already raised a concern, you can raise again as long
    // as the author requested you verify.
    if ($this->isViewerFullyRejected($object, $viewer)) {
      if (!$object->isAuditStatusNeedsVerification()) {
        throw new Exception(
          pht(
            'You can not raise a concern with this commit because you have '.
            'already raised a concern with it.'));
      }
    }
  }

View on GitHub (pinned to 5720a38cfe)

Solutions

1. Ask another user (or a separate auditor bot account) to raise the concern
2. Track your own follow-ups with a Maniphest task or a commit comment instead of the concern action
3. If self-flagging is routine, create a dedicated auditor account for that purpose

if ($this->isViewerCommitAuthor($object, $viewer)) {
  // hide/disable the Raise Concern action for this actor
}

When it happens

Trigger: The commit author selects 'Raise Concern' on their own commit; a bot authored a bad commit and then tries to flag it using the same identity.

Common situations: An author realizes their own commit is broken and wants to flag it for tracking; single-maintainer installs where author and auditor are the same person.

Related errors

• You can not accept this commit because you are the commit au
• You do not have permission to push to this repository.
• You can not accept this commit because you have already acce
• You can not raise a concern with this commit because you hav
• You can not resign from this commit because you are not an a

AI-assisted analysis of phacility/phabricator@5720a38cfe (2026-08-21). Data as JSON: /api/errors/6013a74b7326df6a. Report an issue: GitHub.