Components Changed in a Pull Request

This page explains how to use the Components Changed tab in a pull request (PR) to view, search, and review all metadata components impacted by the change.

The Components Changed tab provides a detailed breakdown of every component that will be merged from the source branch into the target branch. This ensures reviewers can verify exactly what metadata is affected before approving a pull request.

Each component entry shows its type (e.g., CustomField, Layout, Profile) and allows you to drill down into the side-by-side diff view for precise changes.

Viewing Components Changed

1. Open the pull request.

2. Select the Components Changed tab.

3. The list displays:

   • Component name – e.g., ContentVersion.IsAssetEnabled.

   • Component type – e.g., CustomField, Layout, Profile.

   • Search bar – filter by component name.

   • Pagination controls – navigate through all changed components.

Component Diff View

Clicking on any component opens a side-by-side diff view:

• Left side (Target branch) – shows the version currently in the target branch.

• Right side (Source branch) – shows the version from the source branch.

• Highlights:

  • Red (–) – lines removed from the target branch.

  • Green (+) – lines added from the source branch.

This allows reviewers to see exactly what will change when the pull request is merged.

Example

For example, a pull request may include the following change to a CustomField:

• Target branch (main) – contains the field with an old businessOwnerUser value.

• Source branch (FB5) – updates the businessOwnerUser field with a new value.

In the diff view:

• The old line is shown in red with a minus (–).

• The new line is shown in green with a plus (+).

This provides clear visibility into the metadata change being proposed.

Best Practices

• Always review critical metadata types (Profiles, Permission Sets, Layouts) carefully.

• Use the search bar to quickly find specific components (e.g., Account layouts).

• Check compliance and security fields (e.g., sharing rules, permissions).

• If uncertain, use Request changes to flag components needing revision before approval.