Verified commits

Who your commits come from

Each page shows how your saves reach GitHub, above your working branch:

Commits as @your-login with Verified by GitHub

You signed in with GitHub. The editor saves with your own GitHub account, so GitHub records you as the author and signs the commit. Your pull requests and merges are yours too.

Commits as the OpenD app on your behalf

You signed in with your company account (or GitHub sign-in cannot commit for you). The editor's GitHub App makes the commit, with your name and email as the author and a Co-authored-by line. GitHub does not mark these commits Verified.

Repositories that require signed commits

A repository can require that every commit is signed. The editor then shows Signed commits required next to who your commits come from.

• Signed in with GitHub: you save and publish as usual.
• Signed in with your company account: you can still open files and preview drafts, but Save, Create topic and Publish are turned off, and the editor says This repository requires signed commits. Sign in with GitHub to save and publish. Choose Sign in with GitHub, then come back to your file. If there is no such button, ask whoever runs the editor.

On these repositories GitHub itself brings the main branch's changes into your branch, and only when your branch has a pull request: until you publish, the editor shows that the main branch has newer changes, and merges them when you publish. When you resolve conflicts, the editor opens your pull request as a draft so GitHub can merge the main branch in; your choices are saved on top, and nothing is published until you choose Publish.

Messages