Skip to content

merge queue: checking #1887 on main (1d677f9) - #1889

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/563e964d27
Closed

mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/563e964d27

Conversation

@mergify

@mergify mergify Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

#1887 is queued for merge on branch main (1d677f9).

This pull request has been created by Mergify to check the mergeability of #1887.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
all_scopes: false
checking_base_sha: 1d677f94d7fb07502ac738c072de0fc7973bb337
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1887
    scopes: []
scopes: []
...

sileht and others added 2 commits October 5, 2026 18:07
`mergify auth login` sends the machine's hostname as `device_name` so the
approval page can default the token name to this machine. Hostnames often
carry a person's name, and `POST /v1/oauth/device/code` is unauthenticated:
the value sits on the pending grant server-side before anyone approves, so
editing the field on the page does not un-send it. It is also a poor label
for someone with several machines on one account.

`--device-name NAME` replaces the detected hostname and is sent as typed;
the server caps and sanitizes it. A blank value (`--device-name=`, which
also survives Windows PowerShell 5.1 dropping a `""` argument) sends no
name at all, the same request a machine that cannot name itself already
makes, and the server keeps its own default label. Without the flag
nothing changes.

Fixes MRGFY-9268

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Change-Id: If4f977008ded4d2acd0cb1ce5492c60c3f4df4e3
@mergify
mergify Bot deployed to Mergify Merge Protections October 6, 2026 07:45 Active
@mergify
mergify Bot deployed to func-tests-live October 6, 2026 07:45 Active
@mergify mergify Bot closed this Oct 6, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/563e964d27 branch October 6, 2026 07:53

This branch was successfully deployed

2 active deployments
func-tests-live — cc0204e7 Deployed Oct 6, 2026 by mergify[bot] via live-tests #1984
Mergify Merge Protections — cc0204e7 Deployed Oct 6, 2026 by mergify[bot]
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.

1 participant