Onsay Start free

Onsay and GitHub

Approve a change and it arrives in GitHub as a pull request. It never writes to your default branch and it never merges.

Onsay reads what your users tell you, works out which of it is worth doing, and writes the change.

Free to start. No card.

A user said

“every time i log in on my phone it signs me straight back out. happens constantly, i have basically stopped using it on mobile”

Onsay decided

People are being signed out on mobile

Worth doing 95% Your customer 85% A real request 95%

Onsay wrote this

- maxAge: THIRTY_DAYS,
+ sameSite: 'lax',
+ secure: true,

You approve it before any of it ships

Sign in with GitHub and your projects are already listed, with a description filled in for each one. When you approve a change, Onsay opens a pull request against your default branch with the change and the reasoning behind it. It never writes to your default branch and it never merges.

What access it needs

The repo scope, which is what opening a pull request requires. A fine grained token scoped to a single repository works too.

What it does with that access

  • Creates a branch off your default branch.
  • Commits the change and the reasoning behind it.
  • Opens a pull request back into the default branch.

It never writes to your default branch, never merges, and keeps no copy of your source.

Before any of that happens

Nothing reaches your code until you have read what is being proposed and why, and said yes. That gate is the point of the product, not a setting you can turn off.

One that already happened

Something a person actually said, and what it turned into.

every time i log in on my phone it signs me straight back out. happens constantly, i have basically stopped using it on mobile
what came back sign in half a day

People are being signed out on mobile

Worth doing 95%

A signed in person being signed out is a broken core path. Nothing else on the list matters while this is live.

Your customer 85%

An existing paying customer, on the platform most of them use.

A real request 95%

Describes a pattern they can reproduce, and a change in their own behaviour.

What they want
To stay signed in on their phone. This is a report of something broken, not a request for anything new.
Why it matters to them
They have stopped using it on mobile. That is a customer leaving slowly.

What would change

The session is dropped on the redirect back from sign in, which points at the cookie flags rather than the login itself. Fix the flags and add a check so it stays fixed.

shipped 3 files

Keep the session across the sign in redirect on mobile Safari

Three people described the same thing in different words, so it became one change. Sets the session cookie flags correctly and adds a test that fails if this breaks again.

Approved on a Tuesday. Live the same afternoon. You approved it first. Nothing ships without you.

Questions

Does Onsay need write access to my GitHub projects?
Enough to create a branch and open a pull request. It cannot merge, and branch protection on your default branch is untouched.
Can I limit it to one project?
Yes. Use a token scoped to a single repository and connect only that one.

Free to start. No card.

Start free