Ilé ìmọ̀
Ṣẹda fọọmu GitHub token tó kún tẹẹrẹ fún àwọn ibi ìpamọ́ data (repositories) tí o ń gbé sori ẹ̀rọ, kí o sì so ó pọ̀, kí titari (push) le gbé aaye rẹ sori ẹ̀rọ, kí àwọn ẹ̀ka (branches) sì gba àwọn àkọ́kọ́ wo (previews).
Connecting GitHub with a token lets a site deploy from one of your repositories: push to the branch and the site updates. It also lets us publish to GitHub Pages on your account where you choose that as a site's host.
If your repositories belong to an organisation, prefer the Zinn® GitHub app instead — see Install the Zinn® GitHub app. A token belongs to one person and stops working when they leave.
A GitHub account with access to the repositories you want to deploy. If they belong to an organisation, an owner may have to approve fine-grained tokens for it.
On GitHub, click your profile picture, then Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token. Name it and choose an expiration. Under Repository access choose Only select repositories and pick the ones you deploy — the narrowest access that works.
Under Repository permissions give Read and write on:
Press Generate token and copy it — GitHub shows it once.
Open Integrations in your dashboard and choose Connect an account. Pick Code hosting as the group and GitHub as the account, fill in API token, and press Connect account.
We test what you paste before anything is saved. A key that does not work is never stored, and the answer says what was wrong with it. A key that works is kept encrypted in our secrets vault — never in our database — and is never shown again, not even to you.
site's repository connection, pick the repository and branch, and a push deploys.
live site.
source of the site's code.
A repository does not appear. The token's repository access does not include it. Edit the token on GitHub and add the repository.
It worked and then stopped. Fine-grained tokens expire on the date you chose. Generate a new one and connect it; GitHub emails you before a token expires.
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.
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.
Ohun ti a ti n kọ nipa iṣẹ-ayelé, SEO ati ṣiṣe awọn aaye ni iwọn.
Bẹ́ẹ̀ ni agbára ìgbékalẹ̀ ojú-wọ́ ṣe ń nípa lórí ìtọ́kasí ati iye ọna àjápọ̀ ní ọdún 2026: mímú kí àwọn ojú-ewé wà nínú atọ́ka, ṣíṣàyẹ̀wò àwọn àgbàgbà agbègbè wẹ́bù kí o tó kọ́ sórí wọn, ìkọ́ṣẹ́ ọna àjápọ̀ láìfi àlùmọ́lì sílẹ̀, àti òtítọ́ nípa ohun tí agbára ìgbékalẹ̀ le ṣe àti ohun tí kò le ṣe fún SEO.
Ka ifiweranṣẹ naa →Àkọsílẹ aṣeṣe fún WordPress tó yára tí ó sì ní ààbò: ìpamọ́ ipele-súpà, ìpamọ́ ohun ti a ṣe fún ojú-wọ́ọ̀bù kọ̀ọ̀kan, díẹ̀ lára àwọn plọ́gìnnì (plugins) tí ó tọ́ láti lò, bíbójútó ẹ̀rọ náà kí ó wà ní ìsinsìnyí, àti àwọn ojú-ewé WooCommerce tí o kò gbọdọ̀ pamọ́ rárá.
Ka ifiweranṣẹ naa →Ohun tí ó ń yàgbà fún gbígbé ojú òpó wọ́lú tí ó dára kò si sí pẹ̀lú pẹpẹ ìṣàkóso ni — ìṣípòpadà, àwọn àfẹòmọ́, ìpín sọ́tọ̀, ìkójọpọ̀ gidi àti ìwọ̀n gidi — àti bí a ṣe lè ṣe ìdájọ́ rẹ̀ kí o tó ṣe ìpinnu.
Ka ifiweranṣẹ naa →Atilẹyin wà lori gbogbo eto, ile-iṣẹ wa wa ni ṣiṣi fun iwọn wákàtí 24 lojoojumọ, o si le kọwe si wa ni eyikeyi ninu awọn ede wa ti o jẹ 58 — a o sọ fun ọ ni ede rẹ.
Kan si àtìlẹyìn → Gbogbo àpilẹ̀kọ →