@OsirisTerje The package was pushed:

I can see it here

I successfully managed to retrieve it as part of one of my projects.
However, I needed to authenticate with my github token in the nuget.config:

  <packageSourceCredentials>
    <NUnitGitHub>
      <add key="Username" value="PersonalAccessToken" />
      <add key="ClearTextPassword" value="ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" />
    </NUnitGitHub>
  </packageSourceCredentials>

Can you see an accessibility on the packages? Is it marked internal or public?

TODO: Update build.cake to remove BuildSystem.IsRunningOnAppVeyor section and get the version number from the github hash.

Can you see an accessibility on the packages? Is it marked internal or public?

It is marked Private

Also, we need to have the version number incrementing. It now seems to just pick the cake version number. Might be easier to add in gitversion perhaps

Can you see an accessibility on the packages? Is it marked internal or public?

It is marked Private

Can you change accessibility to public?

I changed an org setting, allowing you to push a public package, it was off. I could not find any way of changing it after the push, so I guess you should push it again. Is there a visibility attribute in connection with the push ?

@OsirisTerje I added a git describe version number to the package:

Still working on github actions giving me a proper branch name. The "solutions" I found on the web don't seem to work.
However as we would only really make packages from master it should not be an issue.

I think it still shows private. Do you have a cog wheel that leads to something like the below (which is for my work account):

I see that NUnit3TestAdapter is not listed as private

@manfred-brands I've changed the visibility to public for both NUnit and NUnitLite

Btw, did you try to set up gitversion on to set the version number ?

Btw, did you try to set up gitversion on to set the version number ?

I used git describe based upon an annotated tag.

Would be nice to see it running soon. It makes 4.0 testing more complex as myget dead and we need post-beta1 fixes

Didn't work and no longer relevant.