Code browser and history

Browse a tree

Use the repository tree to move through directories. The current ref stays visible while you browse, so links to files remain reproducible. Open a file to switch between source, rendered Markdown preview, and history where those views are available.

Search for a file or symbol

Use repository file search when you know part of a path or filename. Use code search when you need to find a term across source files or repositories you can access. Search results should be treated as navigation aids: always confirm the selected ref and file path before editing or linking to a result.

Inspect commits and diffs

Open a commit to inspect its message, author, parents, changed files, and file-level diff. The history view can be opened at a branch or bookmark and narrowed to a path.

The diff explorer is useful when a change is large: inspect file boundaries first, then compare the specific hunks that matter. Review the source at the same ref as the change rather than assuming the default branch has not moved.

Keep review context

From a file, commit, or repository page you can move into the associated issue, stack review, or Smartlog. Use those links when handing work to another person so they receive the same source and review context.