FAQ & Common Issues

This guide covers common issues, pitfalls, and their solutions when using Almanax.

Branch Naming

Main vs master

Some repositories use "main" as their default branch, while others use "master". If you're getting a branch not found error, try switching between these branch names.

Repository Access

GitHub repository not found

If you see a GitHub repository not found error:

1. Check the repository URL is correct
2. Verify you have the necessary permissions
3. Ensure the repository exists and is accessible
4. Check your GitHub App installation settings

Scan Issues

Failed and Pending Scans

If a scan fails or gets stuck in pending:

1. Check your internet connection
2. Verify the repository is still accessible
3. Try rescanning the project
4. If the issue persists, contact support

Repository Size

Are there limitations on repository size?

No, Almanax can handle repositories of any size. However, for optimal performance:

• Large repositories may take longer to scan
• Consider using the scan configuration to focus on specific directories or file types
• For very large codebases, you might want to start with a subset of files to establish patterns

How does Almanax handle repository access?

For the complete security model see Security Overview.

Briefly: • OAuth tokens are short-lived. • Repository contents are read to perform analysis. • For CI/CD, the app writes PR comments and updates checks/statuses to report results. • Clones live in a temporary, encrypted workspace and are deleted after each scan. • Findings + minimal metadata are stored; no source code is retained.