Anyone using Source Control (and not update sets) for Updates to OOTB ServiceNow applications?

[Community Alums]

Hello all,

Source control/App Repo seems to be a good option for creating custom applications. This is not about that.

In recent releases, we can actually use source control to track changes to out of the box apps. I work primarily in the scopes associated with VR, SIR and GRC (lots of scopes!) 

Have any of you made the switch away from using update sets completely (except the ones that get auto-generated by source control) and tracking all changes in the studio? I have a customer asking about doing this. I'm not seeing any real advantage. If my testing is correct, I think you need to put items for every scope into its own branch, which seems like a big pain given how many scopes we have - especially in GRC.  I also just feel like my view into "what happened when?" is less visible than looking at versions and update sets. (That could just be that I'm used to update sets.)

Interested in other peoples experiences with this.

Thanks,

Colleen

[zynsn]

Replying to come back later. I am interested in the answers too.

[mnoleal]

Replying as well as I'm interested in best practices if someone already implemented using version control (flow from dev instance to production) then connecting it with CI apps.