How Git and source control work
Understand repository permissions, synchronisation, build identity and source ownership.
Last updated 2026-09-02
What you'll achieve
- Scope repository access
- Resolve source conflicts safely
- Preserve source portability
Repository authority
You choose which repository and branches a BlinkHost installation may access. Installation tokens are short-lived and repository-scoped. Connecting Git does not copy repository secrets, billing resources or unrelated repositories into a project.
Synchronisation and conflicts
BlinkHost records the source revision used for each import and build. A later change on either side is compared with the recorded base before source is replaced. When both sides changed incompatibly, BlinkHost stops and asks for an explicit resolution rather than silently overwriting either version.
Portability
The project manifest describes application roots, build commands, backend modules and declared resources. Source remains exportable. BlinkHost-specific managed capabilities may require an adapter when the same application runs on a different platform, but ordinary application code is not deliberately hidden or made inaccessible.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.