-
Notifications
You must be signed in to change notification settings - Fork 3
Added github workflow action to deploy changes on "push" #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
minor edit (also to test the buildout using github workflow).
- name: Install dependencies | ||
run: | | ||
python -m pip install --upgrade pip | ||
pip install flake8 pytest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why these? They'd be pretty common for actual code, but in this case, we're only building Shinx docs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might as well give it a try.
- uses: actions/checkout@v2 | ||
- uses: actions/setup-python@v2 | ||
with: | ||
python-version: "2.7" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some of thjat code is old, but we probably should go to py3 now
@@ -0,0 +1,26 @@ | |||
name: Code Quality |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I"m not sure running flake8u in this is worth it -- this isn't really a code project.
It would be nice to clean up all the code samples -- some of them are pretty old, but I dont hink we need to run a linter on every merge.
W.r.t to |
No description provided.