Albert Tugushev

@PeterJCLaw > In any case, `git diff --exit-code` works for my use-case, so I'm happy to use that for now. I'm glad to help you. Anyways, i like the idea...

There's another way — use [pre-commit](https://pre-commit.com), see #974.

Also related to the PR #1070 (which is currently under discussion) with the `pip-check` mechanism.

Hello @webknjaz, Thank for the report. See #651 for the detailed info how to deal with different envs.

> Currently, it doesn't seem possible. Am I overlooking something? @webknjaz does the https://github.com/jazzband/pip-tools/issues/826#issuecomment-496242086 resolved the issue?

I see. Unfortunately, it's not possible (at the moment). Currently, pip-tools compiles requirements, evaluates markers and outputs results without ones. The official stance of pip-tools regarding cross-environment usage is that...

Can we postpone this to 6.3.0? There is no rush and i'd like to take a look at this later.

It looks like there is an issue with existing hashes in `requirements.txt`. How to reproduce: 1. Generate hashes first: ```console $ pip-compile --generate-hashes # # This file is autogenerated by...

Confirm :+1: The string "${gitlabSourceName}/${gitlabSourceBranch}" solves my problem too.

@wesleyneal346 thanks for the map!