In case of a mistake while committing a metadata component, what should be done to revert changes?

Using the Re-Create Feature Branch feature is the best approach to revert changes made during the committing of a metadata component. This feature allows you to generate a new feature branch based on the current state of the repository, which effectively undoes any unwanted changes by allowing you to start fresh and isolate the correct changes.

This method maintains the integrity of your version control flow by keeping your commit history intact while providing a clean slate to work from. It also facilitates easier management of the new changes, ensuring that the corrections can be implemented without risking further complicating the commit history.

In contrast, deleting the user story might remove the context and tracking of the changes you made, making it harder to manage past work. Archiving commits would only store them away without resolving the issue, meaning that the erroneous changes would still exist in the history. The Commit Changes feature is not relevant to reverting changes; it is typically used for finalizing and saving changes rather than undoing actions.