dpcx 6 days ago

Because it has the ability to write tests for the PR in question.

Reply View 6 replies
  • tadfisher 6 days ago

    Then it should open a PR for those tests so it can go through the normal CI and review process.

    Reply View 4 replies
    • tedivm 6 days ago

      Doing that requires write access if you're a Github Application. You can't just fork repositories back into another org, since Github Applications only have the permissions of the single organization that they work with. Rulesets that prevent direct pushes to specific branches can help here, but have to be configured for each organization.

      Reply View 0 replies
    • dpcx 6 days ago

      It updates the existing PR with the tests, I believe. They'd still get reviewed and go through CI.

      Reply View 2 replies
      • tadfisher 6 days ago

        Right, the downside being that the app needs write access to your repository.

        Reply View 1 reply
        • rahkiin 6 days ago

          Writing to PR branches should really be some new kind of permission.

          Reply View 0 replies
  • flippyhead 6 days ago

    It's more than that. If can suggest fixes which you can directly commit.

    Reply View 0 replies