-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deployment to github releases from appveyor fails #18
Comments
for now I manually downloaded the wheels from appveyor, and uploaded them manually to both Github and PyPI |
Hey, @anthrotype we talked once that I'll transfer the repo to you. I just tried but I get an error because you have a fork of it. Still want to accept? |
@greginvm yes, that's my fork.. Actually, I'd rather you transfer it to the fonttools organization: |
and thank you! ❤️ |
Hi, I can't transfer to fonttools because I don't have the "create repository" permission. We have 2 options, either I transfer it to you and then you transfer it to fonttools, or you give me create repo permissions in fonttools. Whichever options suits you better :) |
you are now a member ;) |
Nice! :) Repo transfered, tell me if you need anything |
thanks! 🥇 |
Can you do the auto upload to pypi now? |
yes, I'm admin now. I'll do when the time comes to make a new release. The latest is already on PyPI. |
OK, great, i hope it will serve you well 😸 ! If you want you can now remove me from the fonttools org. |
you can stay if you wish :) |
Well, I don't work on pyclipper anymore, so I don't need the membership. Thanks anyway! |
The upload of the generated wheels to Github Releases requires that the admin of this repo, @greginvm, updates the
auth_token
field in the .appveyor.yml file with his Github API key, as explained in the inline comments in that file.I am only a collaborator so I can push tags, but can't generate a new API token, nor I can encrypt it using the Appveyor account that is linked to this repo (that also needs @greginvm privileges).
I am thinking that maybe it's not worth keeping this "upload to github" feature. We simply need the wheels to be uploaded to PyPI, where pip can download them from. Having them on Github is a bonus but not really required.
So if we agree, I can set up Appveyor and Travis to upload the wheels directly to PyPI using my own PyPI credentials (i have access to the pyclipper PyPI account so it should work).
The text was updated successfully, but these errors were encountered: