Git and GitHub-compatible workflows

Use familiar Git commands while relying on Noumena Code for source browsing and review.

Clone

Copy the HTTPS or SSH command from the repository’s Clone menu:

git clone <repository-command-from-noumena-code>
cd <repository>
git status

Authenticate before cloning a private repository. Do not put an access token directly into a saved shell history or a committed remote URL.

Work on a branch

git switch -c feature/my-change
# edit files
git diff
git add <paths>
git commit -m "Describe the change"
git push -u origin feature/my-change

Open the pushed branch in Noumena Code to inspect the source and create a pull request or stack review according to the repository workflow.

Git-compatible review

Pull requests, issues, comments, branches, commits, and file views use familiar concepts so existing teams can onboard quickly. Stack Reviews add a dependency-aware view when a change is better understood as several ordered commits.

When to use another client

Use Sapling when you want stack-native history editing, or JJ when you want stable change identities, first-class conflicts, and an operation log.