Skip to content
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

Ensure that flake8 runs correctly in the CI #425

Merged
merged 2 commits into from
Nov 19, 2020

Conversation

SebastiaanZ
Copy link
Member

Unfortunately, the way we ran the CI meant that flake8 ran on code already merged to master, not on the changes proposed in a PR. This is obviously quite useless and it's been changed now.

I've also split up the workflow into two files.

Unfortunately, the way we previously set up our workflow caused flake8
to run on code already committed to master, not the changes made in a
PR, because it ran in the context of the target branch.

This is obviously useless when it comes to protecting our codebase from
linting errors. I've now set up flake8 in a different way, using
Workflow Commands to create error annotions.

I've also split up the workflow into two separate workflows.
I've also restructured it a bit by using reference links instead of
inline links.
@SebastiaanZ SebastiaanZ added priority: 0 - critical Needs to be addressed ASAP area: CI Related to continuous intergration and deployment labels Nov 18, 2020
@SebastiaanZ SebastiaanZ requested a review from a team as a code owner November 18, 2020 23:50
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 3ce92ea on sebastiaan/backend/fix-flake8-in-ci into d1dfcc1 on master.

@lemonsaurus lemonsaurus merged commit 5236452 into master Nov 19, 2020
@lemonsaurus lemonsaurus deleted the sebastiaan/backend/fix-flake8-in-ci branch November 19, 2020 01:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: CI Related to continuous intergration and deployment priority: 0 - critical Needs to be addressed ASAP
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants