How To Fix SCTS_GITHUB_API006 - Creation of pull request failed. No commits between &1 and &2

SAP Error Message - Details

• Message type: E = Error

• Message class: SCTS_GITHUB_API -

• Message number: 006

• Message text: Creation of pull request failed. No commits between &1 and &2

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message SCTS_GITHUB_API006 - Creation of pull request failed. No commits between &1 and &2 ?

  The SAP error message SCTS_GITHUB_API006 indicates that the creation of a pull request has failed because there are no commits between the specified branches (denoted as &1 and &2). This typically occurs in the context of using SAP's transport management system with Git integration, where you are trying to create a pull request from one branch to another, but there are no changes to be merged.
  
  Cause:
  
  No Changes: The most common cause is that there are no new commits in the source branch (&1) compared to the target branch (&2). This means that the source branch is either identical to the target branch or has not had any new changes pushed to it.
  Incorrect Branches: You may have selected the wrong branches for the pull request, leading to a situation where the source branch does not have any new commits compared to the target branch.
  Local Changes Not Pushed: If you have made