How does Vercel connect to a GitHub repository?

How does Vercel connect to a GitHub repository?

Vercel connects to GitHub through its Git integration, allowing a project to use repository commits as deployment inputs. After the appropriate GitHub access is granted and a repository is imported or connected, Vercel can build changes pushed to that repository. The official GitHub integration guide describes this connection.

The connection links a source-control workflow to hosting. It does not guarantee that every deployed change is ready for users.

Configure the correct application

Select the intended repository and verify the application's root directory. In a monorepo, the wedding frontend may live in a subdirectory rather than at the repository root.

Review the detected framework, dependency installation, build command, and required environment variables. Confirm that the checked-in lockfile and configured runtime match the project's expectations.

Repository access should be limited to what the integration needs, with organization permissions reviewed by the people who manage that repository.

Understand which branch reaches users

By default, the integration creates deployments from pushes, including branch work. The configured production branch controls the usual production deployment path, while other branches support preview review. Confirm the actual project settings instead of assuming the branch must be named main. Vercel documents these branch behaviors.

A useful team workflow is to develop a focused feature on a branch, inspect its preview, complete review, and merge through the repository's established process.

Verify each deployment's identity

Check the deployed commit, build result, environment, and URL. If a wedding editor appears outdated, this evidence helps distinguish an incorrect branch from a caching issue or an unsuccessful build.

When a deployment fails, inspect logs with secrets redacted and fix the underlying configuration or code. Keep production variables separate from previews, and make release readiness an explicit review decision before merging changes into the production path.