Debbie has created a new custom field in Dev1. She commits it on a user story together with the permission set to deploy FLS. After committing the changes, she realizes she forgot to grant the permission set access to the field in Dev1, so she goes back to Dev1 and updates the FLS. What is the easiest way to ensure the FLS is deployed to the next environment together with the field?

Where can you control the available metadata sources when you create a scratch org from a user story?

Debbie and Dave were modifying the same Apex class on their individual sandboxes, Debbie deployed first without any issue, but when Dave tried to deploy, a Git conflict arose, so they teamed up and resolved it manually with Copado's online conflict resolution feature. What happens when both user stories are moved to the next environment?

Dave has set up the following connection behavior in INT:

He has created a new profile in dev1 and is going to commit it on a user story. What will happen after he clicks on Submit Changes?

Debbie committed some changes to the Opportunity Layout but, after deploying her changes from DEV to INT, she found her changes were not there due to an auto-resolved Git conflict she was not aware of. How can she prevent this from happening again in all future promotions?