Daily repository work
Browse repositories and commits
Use Redmine's standard repository interface to navigate source trees, read text files, inspect commit metadata, and review changes.
Navigate the repository tree
Select a repository from the project Repository tab, choose a branch or revision where supported, and open folders or text files using Redmine's normal navigation.
Users need permission to view the project's repository. Creating or changing a repository additionally requires Manage repository, the Repository project module and any creator or per-project limits configured by the administrator.

Read text files
Text files are displayed in Redmine with their repository context. VCSAdmin Git applies its configured file-size and response limits and does not expose binary download through API v1.

Inspect commits
Commit details include stable revision identifiers, parent relationships, author information, timestamps, messages and the changed paths supplied by the repository provider.

Review unified diffs
Open a commit's diff to review text changes. VCSAdmin Git returns the complete API-provided unified diff within its configured response limits.

When repository data looks outdated
The displayed data depends on the provider. Local repositories are read from the configured repository path. GitHub.com repositories are read from the local bare mirror and therefore reflect the latest successful mirror refresh. VCSAdmin Git reads browsing data through API v1 and imports default-branch changesets in bounded batches for Redmine's issue and activity integration.
- Open the repository settings and check the most recent refresh or synchronization result.
- Trigger one manual refresh and wait for it to finish; do not start overlapping requests.
- For GitHub.com, compare the remote head with the bare mirror and check disk space, transport credentials and the refresh lock.
- For VCSAdmin Git, compare the remote head, stored cursor and last error. A large initial history may require several successful bounded runs.
- If the same error repeats, use its request ID and repository identifiers to inspect the corresponding provider log.