-
Notifications
You must be signed in to change notification settings - Fork 54
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
Packetize on pypi #69
Comments
@dwt @celanthe |
Hi @yogeshrnaik and @dwt -- Let me look into this and get back to you! :) I will be OOO after March 1st until March 21st. I endeavor to at least have a preliminary answer for you by Feb. 28th. :) |
Hi @yogeshrnaik and @dwt -- I have a few options for you re: publishing on PyPi.
I would highly recommend the second option, as GitHub Actions is the de facto standard in the Camunda Community Hub for CI/CD workflows. :) If you run into any issues setting up the workflow, feel free to reach out to a member of the DevRel Team by tagging @camunda-community-hub/devrel and someone will get back to you ASAP! |
@celanthe I hear you're saying that you would be willing to give admin permission on this repo to @yogeshrnaik, so he can set up those workflows? |
I can provide admin access for @yogeshrnaik on this repo. |
Are you still looking for assistance here? |
@dwt @yogeshrnaik Is there anything else you need from us here? Otherwise I'll close out this issue and you can open another if there are future things we can help with. |
@yogeshrnaik I was hoping that you would pick up the ball here, this being your repo - can yo please comment? It sounds like the camunda people are well aware of your work and would like to help? |
Hi there, I've noticed that there seems to be a third party providing a package on pypi for this repo:
https://pypi.org/project/camunda-external-task-client-python3/
with the repo: https://github.com/yogeshrnaik/camunda-external-task-client-python3
This seems at least a bit ... strange?
Is there a specific reason you guys cannot provide the package directly? (update guarantees and all)
The text was updated successfully, but these errors were encountered: