On the "Changes" tab, you'll see which metadata was changed in your org. This view updates in near real-time, so as you work in your Salesforce org in another window, for example, through the Salesforce setup or in VS Code, the metadata you touch gets added to the "Changes" tab.

Once you want to store your changes in Git, either for backup reasons or for submitting your work for review or deployment to another environment, click "Pull changes." A dialogue opens showing all of your changed metadata, conveniently grouped by metadata type. It also allows you to opt out of specific files you want to exclude. After making your selection, click "Commit changes." This will send your changes to Git, together with your comment, captured in the "Commit message."

Once you feel ready to move your changes to review – depending on your setup – this may trigger a notification to a group of reviewers or automation to, for example, apply QA (see Hutte's Code Analyzer Recipe for inspiration). Opening a pull request is optional and can be done whenever you have finished your work.

From the “Pull changes” menu item inside the "Project Settings," defaults or placeholders for the individual input fields of the “Pull changes” dialogue can be set.

We ship the feature with the following defaults:

Your users will find their “Pull changes” form with an empty commit message and pull request description, and a pull request title defaulting to the name of your Scratch Org and Sandbox Feature.

By leveraging the “use as Placeholder only” checkbox in combination with a set of variables that we provide, a typical configuration could make the form appear, for example, like this:

With our "Changed File" tab, you can seamlessly manage and navigate the committed changes in your current Sandbox or Scratch Org feature.

Key features: