This is coming from the Source Control class set up in this Namespace.  If you search for "Source Control" in the SMP, and look at the settings for that Namespace you will see that a class is selected.  Change to None if you don't wish to have Serverside (embedded) Source Control active.  If you do wish to use embedded source control, then you will need to provided item type mappings in the ^Sources global in order for it to work (at least to allow the one you currently have active to work - different hooks work differently in terms of configuration)

Ben Spead

I am originally from NH, but have lived in Lancaster, Pennsylvania for the past 21 years.

I am the head of Application Services at InterSystems, where I focus on delighting our prospects, customers and fellow employees with software that saves them time and frustration.

My main areas of focus include enterprise architecture, change control, source control, and process improvement.

I have been attending the InterSystems conference for almost 20 years (DevCon, Global Summit and now READY), and I look forward to connecting with many of you this coming week in Orlando.  Make sure to check out my session on how we are pursuing the use of RAG and AI within InterSystems!

Fun Fact or Hobbies – I love doing outside activities ... hiking, camping, swimming and exploring historical and natural wonders (I am currently writing this from an overnight camping trip with my son).  I am an Eagle Scout, as are my two oldest sons and my third son is well on his way!

@Alex Efa   - I recommend that you take a look at using the Embedded Git open source package, which makes the power of Git available from within an IRIS instance (rather than using it client side which has shortcomings when it comes to things controlled in the SMP like Interop).  

This article may be of interest: https://community.intersystems.com/post/new-and-upcoming-embedded-git-fe...

Here is a helpful branching discussion on options for Embedded Git in our Health Connect Cloud product (the concepts would apply to any application of Embedded Git): https://github.com/intersystems/git-source-control/blob/main/docs/hcc.md.  You will see that it is quite common for developers to work in their own Namespaces on feature branches and then merge them in.  But this is only one of many models.

@Timothy Leavitt, @Pravin Barton  and @Nick Petrocelli can answer specific questions that you may have.