Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

Setup a CI #72

Closed
sobolevn opened this issue Mar 8, 2020 · 2 comments
Closed

Setup a CI #72

sobolevn opened this issue Mar 8, 2020 · 2 comments
Labels
process A change or improvement to the development process

Comments

@sobolevn
Copy link
Contributor

sobolevn commented Mar 8, 2020

Hi, @terrencepreilly! Thanks a lot for your hard work on this project!

I would like to propose adding a CI for this project.
Since it is using tox it should be pretty easy to do.
Here's an example for travis and tox: https://github.com/PyCQA/pep8-naming/blob/master/.travis.yml

Related: wemake-services/wemake-python-styleguide#1138

@terrencepreilly
Copy link
Owner

That seems like a good idea. I'll try to get around to it sometime this week or next.

@terrencepreilly terrencepreilly added the process A change or improvement to the development process label Mar 9, 2020
terrencepreilly added a commit that referenced this issue Apr 9, 2020
At some point, I'd like to get the pre-commit tests up and
running on travis.  But those will be much more difficult
to set up -- they require a good deal of fixtures that
I don't want to add to the repository.

Resolves: Issue #72.
@terrencepreilly
Copy link
Owner

Thanks for the reminder -- I've been meaning to get to this for a while. Running the pre-commits is going to be a good deal more work, but this is pretty good for now.

Resolved in 0d55aa6.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
process A change or improvement to the development process
Projects
None yet
Development

No branches or pull requests

2 participants