`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`
ryanblock opened this issue · 0 comments
Prerequisites
- Put an X between the brackets on this line if you have done all of the following:
- Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
- Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
- Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
- Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
- 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 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 longer master
, but is instead main
, and folks are rightfully encouraged to use main
and not master
, this seems like a reasonable expectation.
Actual behavior:
See above.
Reproduces how often:
Every time.
Versions
MacOS Big Sur 11.5.2
apm --version
apm 2.6.2
npm 6.14.13
node 12.14.1 x64
atom 1.58.0
python 2.7.16
git 2.21.1
Additional Information
- The
master
branch PR (now merged) that allowed the package to be published: architect/atom-package#1 master
branch workaround found here