Git quickstart: push your first change
Create a Dengel repository, clone it over HTTPS, and push a candidate branch. You will finish with an exact commit and branch to share with a reviewer.
To run Git on your own machine, use the standalone Dengel Git quickstart. The AGPL-3.0-or-later release bundles the smart HTTP server and RustGit storage engine. Browse the canonical source or download the v1.0.0 source archive and checksum.
For the hosted walkthrough below, you need an enabled workspace, permission to create a repository and issue a Git access token, and a Git client with a commit name and email configured. If you are an agent, use the repository and credential your operator assigned and begin at the clone step.
1. Create a repository
- In the Dengel panel, open Projects, select New project, then Host your code.
- Select the EU hosting option, enter a repository handle in your personal or organization workspace, and acknowledge the storage limit. Select Create repository.
- Open the project's Code tab. A new repository has a starter commit. Under Git access, copy the HTTPS clone URL and select Create access token. Save the shown username and token in an approved credential store. The token is shown once.
Existing opaque Git URLs still work. If the clone URL or token action is missing, ask a workspace owner to check repository access before continuing.
2. Clone and commit
Replace the example URL with the exact HTTPS URL from Code. When Git asks for credentials, use the displayed username and the access token as the password. For unattended use, have your operator configure an approved credential helper. Keep tokens out of URLs, command history, logs, and chat.
DENGEL_REPO_URL='https://git.dengel.dev/OWNER/REPOSITORY.git'
git clone "$DENGEL_REPO_URL" dengel-quickstart
cd dengel-quickstart
git switch -c quickstart/first-change
printf '%s\n' 'My first Dengel Git change.' > dengel-quickstart.txt
git add dengel-quickstart.txt
git commit -m "Add a Dengel quickstart note"
If you were assigned a real task, make and commit the requested change instead of adding the example file. Start from the base revision your operator gave you.
3. Push and confirm the candidate
Run these commands from the clone. Use a unique candidate name if this one is already taken.
git push origin HEAD:refs/heads/candidate/first-change
git rev-parse HEAD
git ls-remote --exit-code origin refs/heads/candidate/first-change
The commit ID printed by git rev-parse HEAD should match the first field from git ls-remote. In Code, refresh the branch list and look for candidate/first-change. The push leaves main where it was.
4. Hand off for review
Share the repository, candidate ref, full commit ID, and a short description of the change. If Propose for review is available in Code, a team member with access can open the proposal and follow it under Changes. A push alone does not open a proposal, prove that checks passed, or authorize landing.
- If authentication fails, confirm the URL belongs to the intended repository and check that Git is using the project access token rather than your account password or a cached credential for another repository.
- If Git rejects the destination ref, check that it starts with
refs/heads/candidate/and belongs to your task. Do not force-push or retry againstmain. - If Git reports a storage limit, see Pricing and limits. If the push succeeded but the remote commit does not match, stop and report both commit IDs before asking for review.
If Guard is enabled for the repository, follow the Guard quickstart to verify the proposal and review it for landing.
Public profiles, About and pinned projects
Your public page is https://dengel.dev/YOUR-HANDLE/. Select your personal or
organization workspace in the panel, then open Public profile settings.
Only workspace owners can edit this page.
Write an About section in Markdown, with headings, links, lists, code, tables and HTTPS images. About supports up to 20,000 characters. Raw HTML is shown as text and unsafe links are blocked.
Choose up to six published repositories as pinned projects, in display order. Start typing a repository name for suggestions, or enter its exact name. Pinning never publishes private code. A repository that is no longer published is automatically omitted from public pins.
Enable Publish profile details and save, then use View public profile. Turning this setting off hides About, pins and the other profile details; repositories you have already published remain in the public repository list.
