GitHub Sign-in

Flow needs permission to read the pull requests, releases, and workflow runs that your GitHub account can see.

Sign in with GitHub

This is the recommended method.

1. Open Openza Flow and select Sign in with GitHub.
2. Open the GitHub activation page when prompted.
3. Enter the code shown in Flow.
4. Approve access on GitHub, then return to Flow.

Windows protects the saved sign-in information on this PC. Openza does not receive or store it on an Openza server.

Use a personal access token

A personal access token is a private code created in GitHub. Use this option only when the normal GitHub sign-in is not suitable for your account or organization.

1. Select Use personal access token in Flow.
2. Create a token in GitHub settings.
3. Give it access to the repositories and organizations you want Flow to show.
4. Paste the token into Flow and connect.

For a classic GitHub token, select repo or public_repo, plus read:user and read:org. These are GitHub’s permission names.

Caution

Treat a personal access token like a password. Do not share it or include it in source code, screenshots, or messages.

What Flow can see

Flow can show only information available to the signed-in GitHub account. For example, a draft release appears only if that account can view it.

Sign out

Open Settings in Flow and select Sign out. Flow removes the saved sign-in information from this PC and returns to the sign-in screen.