What happens with the previously created commit records in the User Story after recommitting files using the Re-Create feature branch functionality?

When using the Re-Create feature branch functionality in a User Story within Copado, the previously created commit records do not get deleted or remain unchanged. Instead, their status is updated to "Commit not in Branch." This change indicates that while those commits exist, they are no longer part of the active branch associated with the User Story. This feature allows teams to restructure their commits without losing the historical context of previous work, providing a clear record of the changes made and enabling better management of code revisions.

This makes it easy for team members to identify which commits were part of earlier iterations that were not merged or are not currently part of the new branch created after the re-commit action. It's an important aspect of version control within Copado that helps maintain a clean and manageable commit history while allowing for flexibility in development workflows.