Sorry for the late reply, you know... Summer.
We are using pre-commit hooks in our project to apply unified code
formatting with black [1], and then using type annotations combined with
mypy [2], which I gotta say works pretty well.
https://github.com/packit/packit/blob/master/.pre-commit-config.yaml
Feel free to check some PRs to see it in action.
[1]
https://github.com/psf/black
[2]
https://github.com/python/mypy
On Thu, Jul 16, 2020 at 3:31 PM James Richardson <jamricha(a)redhat.com>
wrote:
Hi All,
Vipul and I are looking into several different tools that will allow us to
better analyze our tech debt with any new code that is merged into apps in
http://github.com/fedora-infra.
Currently, we have looked at the tools below, but we would love any and
all input from the team and community on this.
SonarCloud
LGTM
ShiftLeft
Our goal is to find an open source tool that is easy to integrate as well
as providing useful and timely feedback.
So far, SonarCloud has proved to be the one that looks best, but again, we
are very open to any and all suggestions, and at this early stage, a good
conversation to arrive at the best solution.
Regards,
James
--
James Richardson
Engineering Intern
He | Him | His
Red Hat Waterford <
https://www.redhat.com/>
Communications House
Cork Road, Waterford City
jamricha(a)redhat.com <lgriffin(a)redhat.com>
M: +353851970521 <+353877545162> IM: jamricha
@redhatjobs <
https://twitter.com/redhatjobs> redhatjobs
<
https://www.facebook.com/redhatjobs> @redhatjobs
<
https://instagram.com/redhatjobs>
<
https://red.ht/sig>
_______________________________________________
infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org
To unsubscribe send an email to
infrastructure-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedora...