The hold queue
A portal whose Access mode is Open accepts anyone with an email address. The hold queue is what stops that from writing anything a stranger types into your repository.
How it works
Section titled “How it works”The first request from a customer who has never had one released goes to the hold queue. Nothing is written to GitHub. The customer sees that their request was received and is being reviewed.
A member opens the portal’s Hold queue tab and chooses:
- Release — the issue is created in GitHub at the request type’s destination, exactly as if it had been submitted normally, and the customer is emailed that it was accepted. The customer’s next request goes straight through.
- Reject — nothing is created in GitHub and the customer is not emailed. Their next request is held again.
What is not held
Section titled “What is not held”- Requests from customers on an Invite only or Domain allowlist portal. Someone you invited, or someone whose email domain you listed, is not a stranger.
- The second and later requests from a customer whose first was released.
Turnstile
Section titled “Turnstile”The request form carries Cloudflare Turnstile on an Open portal, where anyone with an email address can submit. It is a check the browser passes without the customer doing anything in the ordinary case, and it is what stops automated submissions before they reach the queue at all.
Clearing a backlog
Section titled “Clearing a backlog”The queue is ordered oldest first and shows the customer, their email address, the request type and the title of what they submitted. The rest of what they wrote is readable once the request is released, in the issue itself. There is no bulk release: each one is a decision about whether a person you have never met should be able to write into your repository.