Including a version number in your workspace name automatically checks your workspace into a version control system.

Including a version number in your workspace name automatically checks your workspace into a version control system.

• A. True
• B. False
• C. Not sure
• D. It depends

Answer: (B)

Version control requires an explicit action to capture changes. Merely including a version number in a workspace name is just a naming convention and does not perform a check-in to a version control system. You still need to commit the updated workspace (and any other changes) through your VCS (manually or via an automation hook) for those changes to be recorded in history. So this statement is false because the naming alone does not trigger automatic version control operations.

Version control requires an explicit action to capture changes. Merely including a version number in a workspace name is just a naming convention and does not perform a check-in to a version control system. You still need to commit the updated workspace (and any other changes) through your VCS (manually or via an automation hook) for those changes to be recorded in history. So this statement is false because the naming alone does not trigger automatic version control operations.