
## Leverage local packages when possible

When working with Nuve's personal development environments and installing a repository using abapGit, it's best practice to opt for local packages (those starting with a `$`). This approach eliminates the need for transports.

However, in certain cases—such as when using a custom namespace with sub-packages—creating a transport may be inevitable. Here's how you can handle it:

## Use an existing open transport

If there's an open transport within your backup that fits your needs, you can pass it as a parameter during the pull operation. The command would look something like this:

```bash
${SAPCLI_CONFIG} startrfc -c bapi ZABAPGIT_API_RFC_PULL -S=ABAP_PACKAGE:${ABAP_PACKAGE} -S=GIT_USER:${GH_USERNAME} -S=GIT_PASSWORD:${GH_TOKEN} -S=CORRNR:SIDK900001
```

Remember to replace the placeholder transport number (SIDK900001) with the actual transport number you're using.

Creating a new transport
If you don't have an open transport readily available, you'll need to create a new one. Nuve offers a convenient function module for this purpose:

```bash
${SAPCLI_CONFIG} startrfc -c bapi ZNUVE_CREATE_TR -S=IM_REQUEST_TYPE_V:'K' -S=IM_AUTHOR_V:${SAP_USER} -S=IM_TEXT_V:${REPO_NAME}
```
The request type parameter, `IM_REQUEST_TYPE_V`, is optional. By default, a workbench ('K') transport is assumed, but you can customize it to create a configuration ('W') or a transport of copies ('T').

Ensure the transport is created before calling `ZABAPGIT_API_RFC_PULL` so that it can be passed as a parameter.

Tailoring these commands to your specific use case is critical to maintaining a fluid development environment with Nuve. Remember, flexibility and customization are key to maximizing efficiency.

Managing transports in SAP workflows

Guidance on managing transports within your SAP workflow configuration, including leveraging local packages and creating new transports.

Integrating transports in your workflow configuration

Related support articles

GitHub Actions workflow configuration file

Running ABAP unit tests in GitHub Actions

Setup a GitHub runner