This is an automated email from the git hooks/post-receive script.

unknown user pushed a change to branch dependabot/pip/gunicorn-22.0.0 in repository llvm-lnt.

discards 002f5a9 Bump gunicorn from 19.9.0 to 22.0.0 adds 8b17183 Use python-version matrix (#61) new 2d87edd Fix Dockerfile not using current sources (#60) new 7e62437 Update context directory in Docker workflow new 53ebffe Bump gunicorn from 19.9.0 to 22.0.0

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (002f5a9) \ N -- N -- N refs/heads/dependabot/pip/gunicorn-22.0.0 (53ebffe)

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: .github/workflows/build.yaml | 1 - .github/workflows/tox.yaml | 6 +++++- Dockerfile | 28 +++++++++++++++++++++++++ docker/docker-compose.yml => docker-compose.yml | 6 +++--- docker/.env | 2 -- docker/Dockerfile | 20 ------------------ requirements.server.txt | 4 ++-- 7 files changed, 38 insertions(+), 29 deletions(-) create mode 100644 Dockerfile rename docker/docker-compose.yml => docker-compose.yml (78%) delete mode 100644 docker/.env delete mode 100644 docker/Dockerfile