
The short answer to 'when should you use abapGit with Nuve?' is: always. However, there are certain exceptions where backups might better serve our development workflows. Before diving into the specifics of when to opt for abapGit versus backups, let's first explore the advantages of abapGit and then address its limitations.

## Why are many developers using abapGit?
### Modern developers rely on Git
It's no secret that in today's development landscape, Git is the best practice for source code management. It's the go-to for version control, collaboration, and tracking changes. 

If you're not using Git, you're missing out on a world of streamlined development processes. As a developer, you should continuously keep up with modern tools that make our job easier and improve code quality. abapGit allows you to use Git in SAP systems in conjunction with a Git platform like [GitHub](https://github.com/).

### File-based flexibility
One of the standout features of abapGit is that it's [file-based](https://docs.abapgit.org/user-guide/reference/folders-filenames.html#special-cases). This means your code is saved to files as opposed to being stored in the database. 

The result is that there's no need to persist the SAP instance to save your code, instead, you simply commit the code to GitHub. This offers a level of flexibility and ease that's hard to match. It's a perfect complement to the short-lived SAP instances of Nuve Platform. 

### Fostering creativity and efficiency
With abapGit, handling features, experiments, and bug fixes is much easier. It encourages developers to innovate without the fear of breaking the main codebase. 

You can start a new branch to experiment with a feature. If it doesn't work, you can delete the branch and revert to the original code. However, if the feature works as intended, open a Pull Request. After all checks pass, merge it with the main branch.

### Seamless integration with CI/CD
Continuous Integration and Continuous Deployment (CI/CD) have become staples in modern development. abapGit enables you to integrate your development and deployment processes with tools for CI/CD pipelines, such as [GitHub Actions](https://docs.github.com/en/actions/learn-github-actions/understanding-github-actions).

Setting up GitHub Actions is straightforward. Just add a configuration file. Then, every time you commit code to GitHub, it will activate workflow checks based on your settings.

> ### Stay in the loop! Subscribe now for the latest updates. 📩
> <SubscribeForm />

## What are the limitations with abapGit?
### The abapGit community is active and supportive.
The beauty of abapGit is its wide-ranging compatibility with nearly all objects. While there are a few [exceptions it doesn't support yet](https://docs.abapgit.org/user-guide/reference/supported.html), the key point is "yet".

The community spirit is alive and well with abapGit. If you stumble upon an object that's not available, don't hesitate to [flag it in the issue list](https://github.com/abapGit/abapGit/issues/5912). Even better? Roll up your sleeves and contribute to making abapGit even more comprehensive.

### Config as table data
Some people think abapGit can't handle config. This is not correct. 

Config is essentially table data, and you can indeed save it to abapGit. However, if you've made significant configuration changes, taking a backup might be more convenient.

> ### 💡 Pro tip
> <br/>If you're scratching your head unsure about which tables to use, here's a little hack.
> <br/>First, save to transport. This lets you identify the tables to add to abapGit.<br/>

## When should I use backups?
### Created significant test data
If you have significant test data, for example if you generated SFLIGHT data, it's backup time. While abapGit can handle table data, it doesn't make sense to add thousands of table entries to Git when you have the option to take a backup. 

### Using objects that abapGit doesn't yet support
When using objects that abapGit doesn't currently support, a good workaround is to take a backup. This approach lets you continue working on your project while waiting for the abapGit developer community to add support for that specific object.

### Performing multiple manual steps
A handy rule of thumb? If you're repeatedly going through several manual steps, consider it a cue to take a backup. 

Let's say you have to add three different repositories every time you create a new instance. Rather than repeating this process continuously, do it once, create a backup, and just like that – you've got a ready-to-use starting point.

## Key takeaways
As the world of SAP development evolves, tools like abapGit are leading the charge in fostering efficiency, collaboration, and innovation. Dive in, explore, and let abapGit elevate your development journey!

Happy ABAPing!


A best practice guide on when to use each.

Understand the pros and cons of using abapGit and backups in SAP development on Nuve. Make informed decisions on when to leverage each option for optimal efficiency.

Choosing between abapGit and backups

Related posts

SAP #ABAPfails

Beyond the basics with ABAP platform

Real world example of ABAP unit testing