`apm publish` fails to publish new package from !`master` branch with error: `That repo does not exist, isn't an atom package, or you do not have access` #933
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
Publishing a new package with apm fails with the following error if it is published from a branch that is not named master: That repo does not exist, isn't an atom package, or you do not have access
It may be a factor in this bug that the package was scoped to a GitHub organization (in this case @architect). I did not attempt to publish junk packages to isolate that particular factor.
Steps to Reproduce
Authored repo, tested everything locally, followed the publishing guide, repo is in main branch (note the branch is in green)
Run apm publish patch (in a logged out state)
Authorized Atom to my GH account
Operation fails (see error below); tried again, same result
Confirmed in GitHub my account is properly authorized (it is)
Create a master branch from main
Run apm publish patch again from master, this time it works (again, note the branch is in green):
Merged master branch back into main
Run apm publish patch again, now from main, it works:
Prerequisites
Description
Publishing a new package with
apm
fails with the following error if it is published from a branch that is not namedmaster
:That repo does not exist, isn't an atom package, or you do not have access
It may be a factor in this bug that the package was scoped to a GitHub organization (in this case @architect). I did not attempt to publish junk packages to isolate that particular factor.
Steps to Reproduce
Authored repo, tested everything locally, followed the publishing guide, repo is in
main
branch (note the branch is in green)Run
apm publish patch
(in a logged out state)Authorized Atom to my GH account
Operation fails (see error below); tried again, same result
Create a
master
branch frommain
Run
apm publish patch
again frommaster
, this time it works (again, note the branch is in green):Merged
master
branch back intomain
Run
apm publish patch
again, now frommain
, it works:Expected behavior:
New publishes can be published from any branch, not just
master
. Given the fact that the default branch in GitHub is no longermaster
, but is insteadmain
, and folks are rightfully encouraged to usemain
and notmaster
, this seems like a reasonable expectation.Actual behavior:
See above.
Reproduces how often:
Every time.
Versions
MacOS Big Sur 11.5.2
Additional Information
master
branch PR (now merged) that allowed the package to be published: https://github.com/architect/atom-package/pull/1master
branch workaround found here