Hi there @xenobytezero ????

In GitHub Packages, the scope for a package should match the owner of the repository when publishing to a user account. In your case, since you're publishing to a private repository owned by xenobytezero , you should use the @xenobytezero scope for your package.

However, if you want to use an arbitrary scope (like @ges ), you can create an organisation on GitHub with that name. This would allow you to publish packages under the @ges scope.

To create an organisation and set up the desired scope:

1. Create a GitHub organisation : Follow the documentation on creating a new organisation and choose the name that matches your desired scope (e.g., "ges").

2. Transfer your repository : Transfer your private repository to the new organisation by following the documentation on transferring a repository .

3. Update your package scope : Update your package.json file to use the desired scope:
   "@ges/package-name"

4. Configure your .npmrc or .yarnrc file : Update the registry configuration and authentication set up in your .npmrc or .yarnrc file to use the new organisation scope.

• For .npmrc , update the following line:

  @ges:registry=https://npm.pkg.github.com/
  

• For .yarnrc.yml , update the following lines:

  npmScopes
  :
    
  ges
  :
      
  npmRegistryServer
  : 
  "
  https://npm.pkg.github.com
  "
  

After completing these steps, you should be able to publish packages under the @ges scope using your organisation.

Please note that creating an organisation may require a paid plan to enable private repositories within the organisation.

Hope this helps!