Relevance of Update Sets When Using IDE or SDK with Git Integration

[ArjunBasnet]

In ServiceNow Studio (legacy), when using source control integration (Git) in a scoped application, one should avoid exporting or importing the same application as an update set. Doing so can lead to unwanted consequences.

With modern development using the ServiceNow SDK or IDE, should one still use update set import/export? Or can one rely entirely on the capabilities of the SDK or IDE's Git integration for application versioning?

I believe application deployment should still happen using the Application Repository rather than update sets. Here, I am more concerned about version management and backup.

[Mark Manders]

I think this is the next discussion that developers are already having. The main thing is that there should be one defined way of working for all developers on an instance. You are absolutely right. You only have to deviate one time and quickly move an update set, and you are doomed when the next version is applied through the application repository. The answer (to my best knowledge and experience) is yes, you can rely entirely on those capabilities (for scoped apps), but only if you absolutely make sure everybody does it in the same way.