This should only be called when Pipfile.lock is modified, to avoid unnecessary load for GitHub.
This should help us avoiding merging PRs like #176.
Having dist/ built (and cached) would also be valuable in the future for running end-to-end UI tests (once they're written), so that the CrowdAnki add-on code is exactly in the form it would be on a user's machine.
This should include a test that our dulwich build is pure python.
This should only be called when
Pipfile.lock
is modified, to avoid unnecessary load for GitHub.This should help us avoiding merging PRs like #176.
Having
dist/
built (and cached) would also be valuable in the future for running end-to-end UI tests (once they're written), so that the CrowdAnki add-on code is exactly in the form it would be on a user's machine.This should include a test that our dulwich build is pure python.