Hello Dan,

We are currently using the plugin to notify private repos for an organization using the `account` property without incidents. With your configuration the repo should be at `https://github.com/me/the-repo

What type of credentials are you using? Username password?

Have you tried your credentials at the snippet generator? The error that you are getting is usually generated by invalid credentials or lack of permission.

Are the credentials you are using folder scoped instead of global? If that is the case you may have fall into https://issues.jenkins-ci.org/browse/JENKINS-42955

Here's a screenshot of the snippet generator:

I've also asked on StackOverflow and one theory there is that there might be special characters that are causing problems here. However, I have verified that our password does not have any special characters. The username does if you count "-" (hyphen) as a special character.

Hi – any update here?

Hello, I encountered the same behavior. We use a private GitHub repo. The credentials are rock solid as I'm using the same in Multi-branch Pipeline plugin which is working.

  stages {
    stage("Stage #1") {
      steps {
        githubNotify credentialsId: "github_user", repo: 'my-repo', account: "${GITHUB_PR_SOURCE_REPO_OWNER}", sha: "${GITHUB_PR_HEAD_SHA}", description: 'This is an example', status: 'PENDING', targetUrl: 'https://my-jenkins-instance.com'
      }
    }

I've also tried "repo: https://github.com/my-account/my-repo" but that didn't work aswell.

So, this seems confirmed but we are still not getting any problem with our private repos when using the plugin.

Could you please post here any special character the credentials may be using? For example you can get the real credentials and replace all standard characters to preserve anonymity
Can you try if the plugin works in a multibranch pipeline when using the infer capabilities?

Just to clarify, the account property refers to the owner of the repo which is receiving the PR, in this case it should be the organization. firedanny It seems that as account you are using the owner of the fork, and the SHA is the commit (on the organization's repo) you want to notify, that could be easily found in PR GitHub's UI if you do not want/can`t use the Jenkins variable for it

rarabaolaza, same error when trying Multi-branch Pipeline.

I can confirm credentials (user & password) are all flat with no special chars.

The account is the owner of the repo, repo is set to one of the repos under that account and the SHA is the commit to one of the branches of the same repo. Not a fork.

Is there a way to enable more verbose debugging?

In my case, too, the password and username contain no special characters (there's a hypen in the user name, if that counts). The repo is private, owned by the org, the account property is set to the org name, etc.

We are experiencing this as well. We have special characters in our password but, as we can see from previous comments left by other users, this is probably inconsequential. We have a private repo with an organization and the credentials are verified to have sufficient privileges to set commit statuses.