poetry token set for two repo handles, so users can havea build and a… #13
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
… get repo with different endpoint
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.
… get repo with different endpoint
What?
Why?
When making a repo that gets built with poetry, if you want a dependency to be from the same repo, you have to specify a
/simple version for getting the dependency, this need a separate repo entry in the pyproject.toml with a different name, we'll call the build version mondo-build by default from now on
How?
Testing?
Screenshots (Optional/For UI)
Anything Else?
This only needs to be done for feature PR's. We don't want to slow down fixes and small changes. As a rule of thumb if you are changing more than a few files we need to add context as part of out definition of done.