Manage code in an Axhub repository

When your company uses Axhub repositories — get your app's code onto your computer, push changes to deploy, and reconnect when your sign-in expires.

Depending on your company's setting, your app's code lives on GitHub or in an Axhub repository.
An Axhub repository is a private git repository that AxHub keeps for you. You need no GitHub account or connection, and pushing a change starts a new deploy right away.

Your company admin decides where code is kept. If they change it, apps that already exist stay where they are.

Check whether your app uses an Axhub repository

Open the app console → 저장소 (Repository) tab.

What you seeMeaning
"앱 코드를 보관하고 바뀐 내역을 봐요" (keeps the app's code and its history) with 코드 · 커밋 · Pull requests · 설정 (Code · Commits · Pull requests · Settings) tabsThe app uses an Axhub repository
"앱 코드가 있는 곳과 지금 운영 중인 코드를 확인해요" (where the code lives and what's running)The app uses GitHub — see Deploying automatically on push

From the terminal, use axhub repo status <app>.

statusMeaning
readyReady — the repository URL (repository_url) and default branch (default_branch) come with it
provisioningStill being created. Check again shortly
failedCouldn't be created. The reason comes with it
not_applicableThe app doesn't use an Axhub repository (it's a GitHub app)

How the repository gets ready

In a company that uses Axhub repositories, creating an app creates its repository automatically. You don't make one yourself.

While it's being prepared, the Repository tab shows the steps 저장 위치 확인 → 비공개 저장소 만들기 → 배포 연결 (check storage → create the private repository → connect deploys). A new repository already holds AxHub's starter files as its first commit.

Get the code onto your computer

Click 내 컴퓨터로 받기 (Get it on my computer) at the top right of the Repository tab. It shows the repository URL and two terminal commands you can copy as-is.

1

Sign in to axhub

Run axhub auth login. Repository credentials are issued through this sign-in — it doesn't work while you're signed in with a personal access token (PAT).
2

Connect credentials (once)

Run axhub git setup. It gives this computer's git a credential (valid for 30 days) for Axhub repositories. If you belong to more than one company, pick one with axhub git setup --tenant <company>.
3

Clone the repository

Run axhub repo clone <app>. It clones into an <app> folder under the current folder. To use another folder, add it: axhub repo clone <app> <folder>.
  • Cloned Axhub repository for app … means it worked. A folder that already holds this repository succeeds without cloning again. It won't clone into a folder that holds other files.
  • You can only clone and push over HTTPS. SSH and Git LFS aren't supported yet. A single file can be up to 100MB.
  • App owners, co-owners, and company admins can clone and push.

Push your changes to deploy

Use git as usual in the cloned folder.

cd <app>
git add .
git commit -m "Add due dates to the to-do list"
git push

Pushing to the default branch (default_branch in axhub repo status) starts a new deploy. Pushes to other branches don't deploy. If staging is on for the app, the deploy goes to staging instead of production.

After pushing, the Repository tab → 커밋 (Commits) shows each commit's deploy result — 배포 대기 (pending) · 배포 진행 중 (running) · 배포 성공 (succeeded) · 배포 실패 (failed) · 배포 취소 (cancelled) · 배포 차단 (blocked) · 검사 오류 (scanner error). Click it to open that deploy. If it failed, continue with Reading the logs.

Before pushing, axhub deploy check --app <app> shows problems that would block the deploy — see Check before you deploy. For Axhub repository apps it doesn't check whether the commit is on the remote (unknown), so confirm the push yourself.

When a push doesn't start a deploy

If 배포 기록 없음 (no deploy record) shows next to a commit, that push didn't start a deploy. Common reasons:

ReasonWhat to do
You pushed a branch other than the default branchMerge into the default branch and push
The app has no address (subdomain) yetSet the address first — Address
Another deploy was still runningWhen it finishes, click 최신 코드로 다시 만들기 (Rebuild from latest code) in the app console → 업데이트·공개 (Update & publish) tab, or push a new commit
The app is published but staging is offPublished apps go through staging — Deploy through staging
The app is suspended or archivedBring it back in Manage app state
It's a contest team app under a deploy lockWait until the organizers reopen deploys

Protecting the default branch

In the Repository tab → 설정 (Settings) → 브랜치 보호 (Branch protection) you can protect the default branch: whether people can push to it directly, how many approvals a pull request needs to merge, and whether it must pass the deploy check before merging. App owners, co-owners, and company admins can set this.

When your credential expires

The credential axhub git setup issues lasts 30 days. Running it again keeps a credential with 7 or more days left and only repairs the git configuration, so it's fine to run it out of habit before pushing.

If a push or clone is rejected with a sign-in error:

1

Get a new credential

Run axhub git setup --rotate. It replaces the credential with a fresh 30-day one even if the old one has time left.
2

If your axhub sign-in ended

If you see Axhub OAuth login is required, your axhub sign-in itself has ended. Run axhub auth login first, then the command above again.
3

Push again

Run the same git push again.

If axhub repo clone stops with repository.credential_missing, run the axhub … git setup command shown in the error as-is, then clone again.

You've succeeded when

After pushing, the Repository tab → 커밋 (Commits) shows 배포 성공 (succeeded) next to your commit and your change appears at the app's address.