-
Notifications
You must be signed in to change notification settings - Fork 0
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
Adding a templated release workflow to run on manual dispatch, for no… #21
Conversation
@F-WRunTime did you test this? |
Looks sensible but I will let @tothtamas28 approve - thanks @F-WRunTime! |
I did not realize the workflows and cookiercutter work the way they do. Did some reading and trying to test at least a simple release workflow here that publishes to pypi test. We'll see how this goes. I'm still learning poetry. I am not quite sure I have the release.yml setup such that it best mimics what we'd want to use in our other repository release steps. Simply trying
|
Testing Release is here -- running into some lint check type issues... Used Trusted Publishing > Need to configure Release environment in GH repository and in Pypi account for this to work properly and is unique for every repository publishing here out of our ORG. Notes on setting up a trusted repository in Pypi |
I think this shouldn't be part of the Python template (similar discussion from earlier: #8 (comment)). As a first step, we could add this to the |
Okay. Thanks for the reminder. I will go back and review and conversation. Sounds like we should focus on a more generic approach. I will target methods to work for PYk and K pygments to see what I can do with those. |
In Relation to https://github.com/runtimeverification/devops/issues/108
Adding template for release workflow only with manual deploy execution for python packages
Documentation followed for workflow recommendation by Pypi