Skip to content

docs(agent): document the mut_ user token the API now accepts - #12658

Merged
mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/change-watch
Sep 3, 2026
Merged

docs(agent): document the mut_ user token the API now accepts#12658
mergify[bot] merged 1 commit into
Mergifyio:mainfrom
mergify-ci-bot:docs-agent/change-watch

Conversation

@mergify-ci-bot

@mergify-ci-bot mergify-ci-bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

The API takes a third bearer credential that this page did not mention: Mergify's
own user tokens, prefixed mut_. Anyone holding one had nothing here telling them
it would work, and the caution box listing the endpoints that refuse a personal
access token said nothing about how those endpoints treat a user token.

Adds a short section for it — the prefix, that it comes from the OAuth 2.0 device
authorization grant, and that it resolves to the same person their dashboard
session resolves to, so holding one grants no access its owner does not already
have. The caution box now says the four application-key-only endpoints refuse a
user token just as they refuse a PAT.

Evidence: the engine's bearer scheme for these tokens, which looks a mut_* token
up and returns the same user a dashboard session does; and those four endpoints,
which enable the application-key auth methods and nothing else.

Open question: where a reader gets one. That the device authorization grant issues
it is as far as I could verify — nothing says what to run to start that flow, and
the CLI schema has no login command to point at, so somebody reading this section
still cannot obtain a token. If there is a front door for it, that is the sentence
to add.

@mergify
mergify Bot had a problem deploying to Mergify Merge Protections September 2, 2026 04:19 Failure
@mergify

mergify Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 6 merge protections satisfied — ready to merge.

Show 6 satisfied protections

🟢 🤖 Continuous Integration

  • all of:
    • check-success = build
    • check-success = lint
    • check-success = test
    • any of:
      • check-success = test-broken-links
      • label = ignore-broken-links
    • any of:
      • -head-repo-full-name~=^Mergifyio/
      • check-success=Cloudflare Pages

🟢 👀 Review Requirements

  • any of:
    • #approved-reviews-by >= 2
    • author = dependabot[bot]
    • author = renovate[bot]
    • all of:
      • -head ~= ^docs-agent/
      • author = mergify-ci-bot

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 🔎 Reviews

  • #changes-requested-reviews-by = 0
  • #review-requested = 0
  • #review-threads-unresolved = 0

🟢 📕 PR description

  • body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

@mergify
mergify Bot requested a review from a team September 2, 2026 04:22
Comment thread src/content/docs/merge-queue/lifecycle.mdx Outdated
@mergify
mergify Bot requested a review from a team September 2, 2026 07:28
@mergify-ci-bot
mergify-ci-bot force-pushed the docs-agent/change-watch branch from 624113c to e3165b7 Compare September 3, 2026 05:16
@mergify-ci-bot

Copy link
Copy Markdown
Contributor Author

🤖 I read this review and pushed a new revision.

@mergify
mergify Bot deployed to Mergify Merge Protections September 3, 2026 05:17 Active
@mergify
mergify Bot requested a review from a team September 3, 2026 07:27
@mergify

mergify Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 4 minutes 5 seconds in the queue, including 2 minutes 58 seconds running CI.

Required conditions to merge

@mergify mergify Bot added the queued label Sep 3, 2026
@mergify
mergify Bot merged commit 98769da into Mergifyio:main Sep 3, 2026
9 checks passed
@mergify mergify Bot removed the queued label Sep 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants