AutoDDG on PyPI #5
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
Folks I've already set-up the tokens in the repo! |
simonprovost
requested review from
lyrain2001
and removed request for
lyrain2001 and
roquelopez
Member
Author
|
@lyrain2001 @eduardar: Feel free to review at at your best convenience please :) Cheers |
Member
Author
|
Closing this because I will not have time to resolve the conflicts introduced by a newer PR. If those in charge still want AutoDDG on PyPI, feel free to take over. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi folks!
Hope all is well :)
Here’s a quick PR introducing a lightweight CI/CD setup to publish AutoDDG to PyPI! The CI runs a few key checks — from pre-commit hooks to cross-OS compilation checks (no unit-tests thus far!)— and the CD automatically publishes to PyPI whenever a new version is bumped. Version bumps are handled automatically through the Actions tab: you can trigger a patch (
x.x.N), minor (x.N.x), or major (N.x.x) update, which in turn kicks off the publish workflow to PyPI.I tested everything on TestPyPI, and it’s running smoothly :)
Let me know what you think — this will help with MCPStack-AutoDDG (https://github.com/MCP-Pipeline/mcpstack-autoddg). Also heard that @gracefan2020 started doing some of her research around with AutoDDG — feel free to jump in on the review if you’d like!
Cheers