Collaborate overview

Interactive mind map of how Collaborate at Hart fits together — the same structure as the NotebookLM mind map, hosted in-app so you do not need a Google account. Click branches to expand; linked nodes open related Help guides.

82 topics across sign-in, navigation, roles, workflows, and CLI.

Collaborate at Hart
Private internal code host for HartApps employees and contractors
- What it is
  - Custom VCS web app
    Commits, branches, merges, encrypted blob storage
  - Browse, edit, review, track
    Repositories, issues, pull requests, notifications
  - HartApps SSO
    Sign in with HartApps SSO via Keycloak (auth.hartapps.com)
- What it is NOT
  - Not Git
    No git clone, git push, or .git remote — use collab CLI
  - Not GitHub / GitLab
    Similar concepts, different tooling
  - Not client-facing
    @hartapps.com accounts only
  - Not file-sharing or email
    Use issues, comments, and notifications
- Day one checklist
  - New developer guide
    Pull full project → edit your area → push your branch
  - Sign in with HartApps SSO
  - Home activity dashboard
    Recent commits, issues, and activity
  - Take a tour
    Guided overlay from the top navigation
  - Set up Profile
    Display name, avatar, email preferences
  - Open a repository
    Code tab — file tree and README
- Top navigation
  - Home
  - Notifications
  - Profile
  - Tokens
  - Help
  - Admin
    Global admin only
  - New repo
- Repository tabs
  At /{owner}/{repo}/…
  - Code
    File tree, README, branch selector
  - Commits
  - Branches
  - Pull requests
  - Search
  - Issues
    /{owner}/{repo}/issues — not a repo tab link
- Roles & permissions
  - Reader
    Browse code and issues — no push
  - Maintainer
    Edit, push, open pull requests
  - Org admin
    Soft-delete repositories, org settings
  - Global admin
    Access /admin panel
- Path: Reader
  - Browse Code tab
  - View Commits history
  - Search code at branch tip
  - Read issues and comments
- Path: Contributor
  - New developer workflow
    Pull full project, push your branch, merge to main
  - Create PAT (repo:write)
    Copy fpat_… immediately; Revoke to remove
  - collab pull / status / push
  - Sync vs deploy (push ≠ go-live)
  - Create feature branch
  - Edit file or CLI push
  - New pull request
- Path: Reviewer
  - Watch Notifications
  - Read PR diff
  - Approve · Request changes · Comment only
  - Merge pull request
- Standard team workflow
  Use when branch is protected or review is required
  - Create branch from main
  - Edit in browser or collab push
  - Open pull request
  - Peer review on PR page
  - Merge when approved
  - fixes #N on default branch
    Auto-closes linked issue when merged to main
- Quick browser fix
  Maintainer + unprotected branch only
  - Code → Edit file
  - Commit message → Save changes
- Issue tracking
  - Create issue
  - Add a comment · @mentions
  - Reference #N in commits
  - fixes #N / closes #N
    Only when commit lands on default branch
- Collaboration
  - Presence banner
    Also editing — advisory, not a lock
  - Protected branches
    Opt-in — changes via branch and PR
  - Soft delete & restore
    ~7-day restore window
- collab CLI
  - collab pull owner/repo --dir ./folder
  - collab push owner/repo branch -m "message"
  - COLLAB_TOKEN · COLLAB_URL
  - .collabignore
    Similar to .gitignore
- Help Center
  - Step-by-step guides
    Getting started through administration
  - Acronym table
    PAT, SSO, CLI, RBAC, VCS, and more