autofeat docs
Use autofeat

Portal

What https://portal.autofeat.app does for a repository owner.

Open https://portal.autofeat.app. Sign in with GitHub.

The portal is the owner view of one repository. It does not replace .autofeat/config.yml. Policy is still the file on the default branch. The worker still ignores a repository until an operator has allowlisted the installation and the repository.

What you can do

  • See a readiness checklist for the repository: App installed, config present, labels present, state ruleset present.
  • Open a pull request that adds .autofeat/config.yml (quickstart step 3).
  • Create the four labels (quickstart step 4).
  • Create the autofeat-state-refs ruleset (quickstart step 5).
  • Open a pull request and read its run timeline, including budget spend from the sticky comment.
  • Add or remove autofeat:go, autofeat:pause, and autofeat:stop on that pull request.

Those label buttons are the same labels as Labels. Removing a label does not resume a run. Push a new head, reopen, or re-add autofeat:go. The same-head exception on that page still applies.

Until the operator allowlists both the installation id and owner/repo, the portal shows waiting for operator approval. Labelling from the portal during that wait does not start a run. See Quickstart.

What you cannot do here

  • Change another installation's allowlist. That is operator admin.
  • Call PUT /admin/* or POST /admin/cancel. Those routes use the deployment admin token, not your GitHub session. See Admin API.
  • Read or repair a missing journal ref. Reconcile stays on the operator CLI.
  • Make a pull request branch override policy. The portal edits config by opening a pull request onto the default branch. The run uses the default branch head after that pull request merges.

Operator admin

Operators see which installations and repositories are allowlisted, and whether the deployment is paused (pause_all). Approval is an operator action. A repository owner sees the waiting state until both names are allowed. The portal does not hand the admin token to a signed-in repository owner.

On this page