Getting started

Push your first repo to Gluecron in under 60 seconds. No special tooling required — just git.

1. Create an account

Head to /register, pick a username and password. Your username becomes part of every repo URL:gluecron.com/<username>/<repo>.

Verify your email when the one-time link arrives. Verified addresses receive issue, PR, and gate-run notifications.

2. Create your first repo

From the dashboard hit + New, or visit /new. Choose:

• Name — lowercase, hyphens OK, no spaces.
• Visibility — public (anyone can clone) or private (only you and collaborators).
• Initialize with README — tick this so you get a default branch immediately.

3. Push an existing local repo

Add gluecron as a remote and push your default branch. Replaceyou and my-project with your actual username and repo name.

# Add the remote
git remote add origin https://gluecron.com/you/my-project.git

# Push (first time — track the upstream branch)
git push -u origin main

Git will prompt for your username and password. Use your Gluecron password, or better yet a personal access token (tokens start with glc_ and never expire until revoked).

4. Clone an existing repo

git clone https://gluecron.com/you/my-project.git
cd my-project

5. Skip the password prompts

SSH clone is not enabled on this host, so stay on HTTPS. To avoid typing a password on every push, use a personal access token as the password and let your git credential helper remember it:

git config --global credential.helper store   # or: osxkeychain / manager
git push   # enter your glc_… token once; git remembers it

6. Import from GitHub

Already have repos on GitHub? Visit /import, paste the GitHub URL (public or private), and Gluecron mirrors the full history, branches, and tags in one shot. Subsequent pushes go to Gluecron directly.

What happens after push?

Every push to the default branch triggers the post-receive hook:

• GateTest scan — checks the diff for leaked secrets, dependency advisories, and policy violations. Results appear on the commit page within seconds.
• AI review — if the push targets an open PR, the AI reviewer comments on changed files automatically.
• Workflow runs — any .gluecron/workflows/*.yml files with a push trigger fire immediately.
• Webhooks — registered webhook URLs receive a push event payload within ~1 second.