What determines an existing component in Copado during a commit?

In Copado, the determination of whether a component is considered "existing" during a commit is based on its presence in the feature branch files. When a component is found in the feature branch, it indicates that it is part of the current changes being reviewed and committed. This is essential because the commit process directly interacts with the items tracked in the feature branch, which reflects the planned changes.

Components that are marked for deletion, represent previous versions, or lack dependencies do not influence their status as existing components during a commit. Instead, what matters is their inclusion in the specific branch being worked on. By checking the component against the current version in the feature branch, Copado ensures that commits are made with accurate and up-to-date components, which is vital for maintaining the integrity of the codebase during deployment processes.