User Stories - Git Metadata

Updated 9 months ago by Iván Minaya

If you are upgrading from a previous version, make sure that you have set the Field Level Security and Object Level Security for your profiles and permission sets.

Copado integrates with Git in many ways. From a User Story, users will be able to select multiple commits and relate them to it. By clicking the button "Add Commits" users will be able to select one or more commits which then will be displayed under the "User Story Commits

Another way to add commits to a User Story is using the button "Commit Files" which will prompt the user to select one or more files from the salesforce Org where the development is being done and a Commit Message. This will automatically retrieve the metadata and create a new commit on the git repository, and finally creates the User Story Commit automatically. Copado will need  to know the Org - Repository - Branch to orchestrate the integration, users only need to create a "Git Snapshot" record which will relate these 3 items  (1 time process). Copado will automatically find the Git Snapshot record based on the Org where the User Story is seated and if more than one is found, Copado will ask the user to choose one.

When using the Promotion process, Copado will combine the Metadata (typically configuration) and Git Metadata (typically code) to produce one single Deployment record which will contain multiple steps. See Promotions.

If "Add Commits" or "Commit Files" or "User Story Commits" related list are not displayed on the user story, please edit the User Story layout.

Feature branches

When using CCM and CBM, aka the Copado Git Flow, copado will create feature branches for each User Story automatically when using the "Commit Files" button on the User Story record.

The branch will be called "feature/{user-story-number}" and it will be created out of the Main branch of the Deployment Flow, typically "master", the selected files will be committed in the feature branch and then merged into the Org's branch, based on the Org where the User Story is being developed and the branch assigned to that Org in the Deployment Flow. The result is, an isolated feature branch that has only the changes of the User Story, and Org branch which is in sync with the Org's metadata.

Retrieve Only

As from Copado v7, with the "Retrieve Only" checkbox, you will be able to pull OLS/FLS for Profiles and Permission Sets, without having to commit/deploy the original fields or objects.

This feature gives you a more granular control over Profiles and Permission Sets in regards to Objects and Fields permissions.

How to use it:

Go to a Git Snapshot or a User Story. Click on the "Commit Files" button. Notice the new "Retrieve Only" checkbox. Select this checkbox for the objects you want to pull OLS, but avoid its deployment.


  • As from Copado v7.1, merge conflicts are auto-resolved by Copado. Click here for more information.

How did we do?