Repository navigation
Persist credentials and add configurable Git timeouts - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Git operations now use a configurable global timeout (15 minutes by default), with per-repository inheritance or 15/30/45/60-minute overrides. The selected budget is captured when a task starts and can be changed without restarting the service.
Credentials now survive host replacement through database-backed storage for encryption material, service API credentials and OAuth client configuration. The first upgrade imports an existing credential key so saved code-source tokens remain readable; users can replace unreadable credentials through the UI. Existing database values take precedence over bootstrap environment variables. MCP sessions also work behind a reverse proxy when the application listens on a network interface.
Validation: full Go suite, targeted race tests, JavaScript checks, web/native builds, public-artifact audit, and a local startup/restart smoke test confirming persisted API authentication without a key file. Added SQLite migration/restart coverage and shared PostgreSQL/MongoDB storage-contract coverage for CI.