ຕິດຕັ້ງແອັບ Zinn® GitHub ເພື່ອໃຫ້ພວກເຮົາສາມາດນຳໃຊ້ໂດຍບໍ່ຕ້ອງໃຊ້ໂທເຄັນທີ່ມີອາຍຸຍືນ

What connecting it does for you

Installing the Zinn® GitHub app lets a site deploy from your repositories — and a project board stay in step with GitHub — without handing us a personal token. We hold only the app's installation number, which is useless on its own, and mint a token that lasts an hour each time we need one. It is the better choice for an organisation, because it does not belong to any one person and does not stop working when someone leaves.

Before you start

A GitHub account, or owner rights on the organisation where you want to install the app. Organisations that forbid third-party apps need an owner to allow it; if that is not possible, use a fine-grained token instead (Connect your GitHub account).

1. Create the key at GitHub

There is no key to create. Install the Zinn® GitHub app on your personal account or your organisation, and choose either all repositories or only the ones you want us to deploy.

Then find the installation number:

• Personal account — Settings → Applications → Installed GitHub Apps, and Configure

next to the Zinn® app.

• Organisation — Your organizations → Settings → GitHub Apps, and Configure next to

the Zinn® app.

The number at the end of the address bar on that page — for example github.com/settings/installations/12345678 — is the installation number.

2. Connect it here

The app is chosen where it is used rather than on the Integrations screen:

• On a site's repository connection, choose GitHub (app install).
• On a project board's GitHub link, choose The Zinn® GitHub app.

Paste the Installation number and continue. We check the installation before saving anything; a number we cannot reach is never stored.

What happens next

• The repositories you granted the app appear for the site to deploy from, and a

push deploys it.

• Every action we take appears in the installation's audit log on GitHub under the app's name,

not yours.

• To give us more repositories, change the app's repository access on the same Configure

page — nothing needs reconnecting.

If it does not connect

A repository is missing. The installation only covers the repositories you chose. Open Configure and add it.

The number is refused. Check it is the installation number from the address bar, not the app's own ID, and that the app is still installed — an uninstalled app has no installation.

It says the key was rejected. Almost always one of three things: a space or a line break copied with it, a key that has expired, or a key that was revoked or regenerated after you copied it. Create a fresh one and paste it again.

It connects, but something later fails. The key authenticates but lacks a permission the action needs. Create a new key with the permissions listed above, then disconnect the old connection and connect the new key.

Disconnecting

Open Integrations, find the account and press Disconnect. That deletes the stored key at once. Anything that was using it stops at its next action, and the screens that depended on it say so rather than failing quietly.

Disconnecting does not undo what was already done — records, deployments or settings we changed on your account stay as they are. If you think the key itself may have leaked, also revoke it at the vendor; disconnecting removes our copy, not theirs.