Skip to content

Commit

Permalink
Update pull_request_coverage.yml
Browse files Browse the repository at this point in the history
  • Loading branch information
Inspirol committed Jan 11, 2024
1 parent cbfd346 commit ee928bd
Showing 1 changed file with 12 additions and 54 deletions.
66 changes: 12 additions & 54 deletions .github/workflows/pull_request_coverage.yml
Original file line number Diff line number Diff line change
Expand Up @@ -20,65 +20,23 @@ jobs:
with:
fetch-depth: 1

- name: Set up Python 3.11
- name: Set up Python 3.12
uses: actions/setup-python@v1
with:
python-version: 3.11
python-version: 3.12

# Cache the installation of Poetry itself, e.g. the next step. This prevents the workflow
# from installing Poetry every time, which can be slow. Note the use of the Poetry version
# number in the cache key, and the "-0" suffix: this allows you to invalidate the cache
# manually if/when you want to upgrade Poetry, or if something goes wrong. This could be
# mildly cleaner by using an environment variable, but I don't really care.
- name: cache poetry install
uses: actions/cache@v2
with:
path: ~/.local
key: poetry

# Install Poetry. You could do this manually, or there are several actions that do this.
# `snok/install-poetry` seems to be minimal yet complete, and really just calls out to
# Poetry's default install script, which feels correct. I pin the Poetry version here
# because Poetry does occasionally change APIs between versions and I don't want my
# actions to break if it does.
#
# The key configuration value here is `virtualenvs-in-project: true`: this creates the
# venv as a `.venv` in your testing directory, which allows the next step to easily
# cache it.
# - uses: snok/install-poetry@v1
# with:
# # version: 1.1.12
# virtualenvs-create: true
# virtualenvs-in-project: true

- run: pipx install poetry
# Cache your dependencies (i.e. all the stuff in your `pyproject.toml`). Note the cache
# key: if you're using multiple Python versions, or multiple OSes, you'd need to include
# them in the cache key. I'm not, so it can be simple and just depend on the poetry.lock.
- name: cache deps
id: cache-deps
uses: actions/cache@v2
with:
path: .venv
key: pydeps-${{ hashFiles('**/poetry.lock') }}

# Install dependencies. `--no-root` means "install all dependencies but not the project
# itself", which is what you want to avoid caching _your_ code. The `if` statement
# ensures this only runs on a cache miss.
- run: poetry install --no-interaction --no-root
if: steps.cache-deps.outputs.cache-hit != 'true'

# Now install _your_ project. This isn't necessary for many types of projects -- particularly
# things like Django apps don't need this. But it's a good idea since it fully-exercises the
# pyproject.toml and makes that if you add things like console-scripts at some point that
# they'll be installed and working.
- run: poetry install --no-interaction
- name: Install dependencies
run: |
python -m pip install --upgrade pip
python3 -m pip install robotpy
pip install coverage
python3 -m robotpy sync
# And finally run tests. I'm using pytest and all my pytest config is in my `pyproject.toml`
# so this line is super-simple. But it could be as complex as you need.
- run: poetry run coverage run --branch robot.py test --coverage-mode
- name: Run Coverage
run: |
coverage run -m robotpy test
- run: poetry run coverage xml --omit=mechanism_setup.py
- run: coverage xml --omit=mechanism_setup.py

- name: Get Cover
uses: orgoro/[email protected]
Expand Down

0 comments on commit ee928bd

Please sign in to comment.