Demo request
RB-DR/01 · sheet 1 of 1

See it hold a real merge

A demo is one pull request on one of your own repositories, reviewed end to end: the findings it raises, the ones it suppresses and why, the check going red, and the merge released on a signature.

Four fields. No account, no install, and nothing runs against your code until you say so.

01

You raise the slip

The slip is sent the moment you raise it. No mail client, no account, and no copy kept on this page.

02

We agree a repository and a window

Read access to one repository, for as long as the demo runs. A fork or a scratch copy is fine and is what most people pick.

03

You watch one pull request go through

Roughly thirty minutes, live. You see the findings, the triage decisions, the comments it chose not to post, and the certificate at the end.

Request for demonstration RB-DR/01
Enter a name we can address the reply to.
Enter an address the reply can reach.
Check this field.
Say roughly what it would be pointed at.
Check this field.

Sent straight to a person. Your address is used to reply and for nothing else.

Request raised RB-DR/01 · awaiting reply

It is on its way to a person, not a queue. Replying to this slip means replying to you: the address below is where the answer goes.

Raised by—
Reply goes to—
Typical replywithin one working day

Nothing else to do. If you do not hear back within a working day, — a duplicate is easier to deal with than a request that never arrived.

On what this page does with your details
RB-DR/01

Raising the slip posts what you typed to one function on this site, which sends it on as a single email and keeps nothing. There is no database, no analytics on this page and no third party in the path beyond the mail provider that carries the message. Your address is used to reply to you and for nothing else. Close the tab before you raise it and the request simply never existed.