

- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
In another blog I talked about App Repo and how it works. Here we will discuss Git Repo and how to use it. Anyone can get a Git Repo for personal use. If you haven’t used one previously, it might be fun to try out.
Git Repository
- External source control integrates with platforms like GitHub, GitLab, Bitbucket, Azure Repos, etc.
- Provides source control for application code (scripts, UI pages, configuration files).
- Usage:
- Developers can commit, branch, and merge code outside ServiceNow.
- Useful for collaboration, code review, and CI/CD pipelines.
- Versioning managed by Git (branching, tags, pull requests).
- Best for teams that want modern DevOps practices and external version control outside of ServiceNow.
Difference between App Repo and Git Repo
- App Repo = Move packaged applications (Scoped app) between ServiceNow instances (deployment).
- Git Repo = Manage code outside ServiceNow with standard DevOps workflows (development lifecycle).
In my blog “Need to build a new Workspace” I showed you that there was an option to Import App from Git
If you haven’t used GIT branching, it can get very complicated. Below is an example. Master is typically where everything ends up at some point after it’s been tested and approved.
Again, my suggestion is to get your own GIT and a PDI and test it out for yourself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.