-
Notifications
You must be signed in to change notification settings - Fork 5
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
add(ci): GitHub workflow to package plugin on CI/CD #22
add(ci): GitHub workflow to package plugin on CI/CD #22
Conversation
Oh nice! Tbh we do not have a technical account for this yet but all our plugins are maintained by different people and their accounts... It's something we were just discussing internally the other day. Is there a standard process that you can recommend? Does OSGeo allow technical accounts? I'd like to not use my personal account for this. |
We use the For a few months, API token are available but it's still not supported in QGIS Plugin CI (opengisch/qgis-plugin-ci#285). |
2b5802b
to
4f496b2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again every thing looks OK to me 🚀
I have set up the secrets with my personal account for now and switch to the technical account once we have it. |
To be merged after #21
In this PR, a GitHub workflow to:
@kannes to make the workflow work, you have to set your plugins.qgis.org credentials as GitHub Actions Secrets (
OSGEO_PASSWORD
andOSGEO_USER
). Screenshot from QTribu: