-
Notifications
You must be signed in to change notification settings - Fork 424
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 pipx install github pull request support #812
Comments
Why would an end user want to install from a pull request? This seems like an exceedingly rare use case. |
developer: can you test this fix from this pull request? |
@cs01 This would be incredibly helpful. Here's an example: python-poetry/poetry#4852 (comment)
When there's an bug or improvement, this can be used to get the users in the issue to test the pull request easily. This saves a ton of effort. I'm stunned this doesn't already exist. 🤷 I'm fine with doing it manually in the mean time by hand, but when reviewing lots of PRs this would save time. Edit: NPM / yarn has a convention for this at https://stackoverflow.com/a/36743127/1396928 |
The
Perhaps that is the first thing to resolve.
|
Update: This usage works:
But projects need to be installable from git branch: |
@glensc Perhaps make a PR to add it to README / docs and see what the feedback is? I think others would find it helpful |
As a user myself, I'm a bit confused why I can't just run something like: pipx install git+https://github.com/simons-public/protonfixes when doing it with |
@gaborbernat your last message is truncated (or not formatted properly) this is what I see |
While this is doable, would require us integrating against the GitHub API, which makes me nervous because then tomorrow a GitLab user would show up, and where would that end? As such, I'm currently -0.1 on doing this.
This works and is not Git server dependent. |
What I see what needs to be done here is to document this experience: and by "But projects need to be installable from git branch" I mean that I needed to make changes in code not to rely on CI part that generated version, i.e. version would have some default. |
i also found need to use |
Currently not installable from source because version "Uknown" does not parse. Refs: - pypa/pipx#812 (comment)
here's more minimal changes needed to be able to install from source: it relied CI to fill |
How would this feature be useful?
pipx is for end users. end users typically don't understand how to figure out repo and branch of a pull request
Describe the solution you'd like
Describe alternatives you've considered
The alternative, the current is to:
and even advanced users have trouble doing that:
oh, glad I picked that example. some shells may need to deal with escapes, like
#
for UNIX,^
for windowsalso, once the PR is merged, and the branch deleted the branch name option won't work, would need to use git hash of the last commit or merge commit.
for initial implementation having support for open PR's would be already big step forward.
The text was updated successfully, but these errors were encountered: