PyData #10, Krakow: Configuring python linting to be part of CI_CD using GitHub actions

1. Configuring python linting to be
part of CI/CD using GitHub
actions
Illia Todor

2. Bio
Past: Big Data Engineer
Present: DataOps

3. Why do we need linters
- eliminate potential errors
- bugs
- stylistic errors
- enforce the common code style across the team

4. Linters
- flake8 with its plugins
- black
- isort

5. All in once
FlakeHeaven: It’s a Flake8 wrapper to make it cool ©
FlakeHeaven supports all flake8 plugins, formatters,
and configs

6. black config

7. isort config

8. flakeheaven config

9. flakeheaven plugins

10. unwanted checks

11. disable documentation stuff

12. import checks

13. disable import-error

14. airflow tweaks

15. line break

16. disable W503

17. statement has no effect

18. disable W0104

19. all the checks disabled so far

20. GitHub actions jobs
checkout
linter deps
installation
filter python files run linter

21. When to run it

22. What files does it run against

25. time to run linter

28. success story

29. q&a
dev.to article github/iamtodor linkedin/iamtodor