Skip to content
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

Define git branch for package from environment variable? #2391

Closed
typhoon2099 opened this issue Jun 20, 2018 · 2 comments
Closed

Define git branch for package from environment variable? #2391

typhoon2099 opened this issue Jun 20, 2018 · 2 comments
Labels
Type: Duplicate This issue is a duplicate of an already-existing issue.

Comments

@typhoon2099
Copy link

It it possible to define an environment variable to be used to determine the branch that should be checked out for a git repo used as a module? I have been trying to edit my Pipfile to include this but I'm not having any success. Here's an example error message:

pip9.exceptions.InstallationError: Command "git checkout -q ${PIPENV_ENVIRONMENT}" failed with error code 1 in /tmp/pip-1kIzTE-export

The reason that I'm doing this is that I have two deployments (staging and master) and would like the packages that are pulled in to use the same branch as the repo that is pulling them in (so the master branch would pull in master packages and the staging branch would pull in staging packages).

@uranusjr
Copy link
Member

merging into #2317

@uranusjr uranusjr added the Type: Duplicate This issue is a duplicate of an already-existing issue. label Jun 20, 2018
@notEvil
Copy link

notEvil commented Jul 9, 2018

second @typhoon2099
specifying targets (branch, ref or even version) dynamically simplifies version and dependency management a lot.
It was possible to use environment variables in packages section up until v2018.05.18 but was dropped thereafter as it seems. Even though I understand why, it would have been very nice :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Duplicate This issue is a duplicate of an already-existing issue.
Projects
None yet
Development

No branches or pull requests

3 participants