What is the status of previously created commit records in a user story after using Re-Create feature branch?

When the Re-Create feature branch functionality is used in Copado, any previously created commit records within the user story are marked as "Commit not in Branch." This action indicates that the previous commits exist but are no longer part of the new branch resulting from the re-creation process. This feature is particularly useful for managing and maintaining the integrity of version control within user stories, allowing teams to refresh or modify branches without losing track of previous work.

The re-creation of the branch often arises due to the need for a clean or updated version, leading to this specific marking of the earlier commits instead of outright deleting them, which preserves the history and context of development efforts. Other options, such as the status remaining unchanged or being deleted, do not accurately reflect the functionality provided by the Re-Create feature branch. Additionally, reverting to a previous version suggests a different action wherein changes are rolled back, which is not what occurs when re-creating the feature branch. Thus, marking previous commits as "Commit not in Branch" effectively helps to maintain clarity in version history while allowing developers to work with an updated branch.