Git Integration: Native → Git (GitHub)

This page explains how Native → Git synchronization works, allowing Salesforce metadata managed in Revvy branches to sync with GitHub for full version control.

Revvy supports seamless integration with external Git providers for version control. Currently, GitHub is supported for Native → Git synchronization. This allows Salesforce metadata managed in Revvy branches to sync automatically with GitHub repositories, ensuring full version control alongside Revvy’s DevOps workflow.

Accessing Git Integration

Navigate to Settings → Git Integrations in the Revvy DevOps app. Two integration options are available:

• User Stories Integration – Connect Jira or other story management platforms.

• Git Integrations – Connect Git repositories for synchronization of branches, commits, and pull requests.

Configuring GitHub Integration

1. Go to Settings → Git Integrations → Integration.

2. Select Service Type = GitHub.

3. Enter:

   • Organization – GitHub org or owner.

   • Token – Personal access token (with repo + workflow scopes).

   • Username – GitHub username.

   • Repository Name – Target GitHub repo.

4. Click Connect.

   • On success, you’ll see a confirmation: “Git integration settings were saved successfully.”

   • Once connected, a Disconnect button replaces the Connect button.

Activities – Synchronization History

After setup, Revvy logs all Git synchronization jobs under Settings → Git Integration → Activities.

Filters

• Branch Filter – Select a specific branch (e.g., Feature-JiraStory1).

• Direction – Options include:

  • Native → Git (from Revvy to GitHub).

  • Git → Native (future expansion).

• Status – Filter by job statuses (Queued, In Progress, Completed, Aborted, Exception).

• Date Range – Narrow results by time window.

Synchronization History Columns

• Timestamp – When the sync started.

• Branch – The Revvy branch name.

• Direction – Flow of sync (Native → Git).

• Status – Current job state.

• Components – Summary of New, Changed, and Deleted items.

• Duration – Total run time.

• Logs – “See Logs” link opens details.

Job Statuses in Git Integration

• Queued – Sync scheduled, not yet started.

• In Progress – Sync running; click to view components and logs live.

• Completed – Sync finished successfully.

• Exception – Sync failed with an error (check logs).

• Aborted – Sync stopped manually.

In-Progress Jobs

When a job is In Progress, you can:

• Click the Direction (Native → Git) link to view synchronized components.

• Open the Logs panel to see real-time execution (repository setup, component synchronization, project creation).

• Use the Refresh button to load new log lines.

Completed Jobs

When a job has status Completed, you can:

• Review Job Summary including:

  • Branch name.

  • Job status (Completed).

  • Direction (To Git).

  • Total synchronized components (New, Changed, Deleted counts).

  • Duration.

  • Date started and date finished.

• Open Logs to see the full step-by-step history:

  • Job started.

  • Prepare Git repository started/completed.

  • Component synchronization started/completed.

  • Push to Git repository started/completed.

  • Job completed.

• Use the Refresh button to reload updated logs if you’re reviewing shortly after completion.

• Click into Synchronized Components to view:

  • All synced items, with filters for New, Changed, Deleted.

  • Component type filter (CustomField, CustomObject, ListView, etc.).

  • Search bar for locating a specific component.

  • Last updated metadata in Revvy vs. Git.

This ensures full traceability: you can confirm exactly which components were pushed, validate no changes were missed, and review logs for audit or troubleshooting.

Synchronized Components View

Clicking a job or Native -> Git opens the synchronized components panel:

• Tabs: All, New, Changed, Deleted.

• Filters: By component type.

• Search: Narrow results by name.

• If no components are updated, the panel shows “No components.”

Synchronization Logs

Detailed logs provide insight into the sync process. Example entries include:

• Job started.

• Prepare Git repository started/completed.

• Component synchronization started.

• Create Salesforce project started/completed.

Logs can be copied via the copy icon and refreshed for live updates.

Aborting a Sync

If needed, an active sync can be aborted:

• Open the job detail.

• Click the Abort button.

• Status updates to Aborted, and the job stops immediately.

Viewing Synced Content in GitHub

Once synchronization jobs are Completed in Revvy, the connected GitHub repository reflects the updated branch state.

Branches in GitHub

Each Revvy branch (e.g., Feature-JiraStory2) is created or updated as a branch in the GitHub repository.

You’ll see the branch name listed in the branch selector dropdown.

Commits in GitHub

Revvy pushes commits with messages like “Devops sync. A branch is synced.”

Each sync job creates a new commit for traceability.

Repository Structure in GitHub

The repo is formatted as a Salesforce DX project with standard folders (force-app/, config/, scripts/) and files (sfdx-project.json, package.json, README.md).

Best Practices

• Use Personal Access Tokens with limited scope for security.

• Use branch names with only letters, numbers, _, /, -, and ., and avoid spaces or special characters to ensure smooth Git synchronization.

• Monitor Activities for exceptions and resolve quickly.

• Use filters to audit specific branches, dates, or statuses.