From 09106387b8ad85064ea56624891dd0caf6346048 Mon Sep 17 00:00:00 2001 From: Oliver Beckstein Date: Tue, 15 Dec 2015 11:33:59 -0700 Subject: [PATCH] link to issue #583 were necessary; more accurately summarized qc's capabilities at top --- quantifiedcode.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/quantifiedcode.md b/quantifiedcode.md index d7f4ea5d565..dabb603a544 100644 --- a/quantifiedcode.md +++ b/quantifiedcode.md @@ -1,6 +1,6 @@ [![Code Issues](https://www.quantifiedcode.com/api/v1/project/829d7d4b95d04111b38451d14101545d/badge.svg)](https://www.quantifiedcode.com/app/project/829d7d4b95d04111b38451d14101545d) -[quantifiedcode](https://www.quantifiedcode.com/) is a tool that checks code for best practices and finds bugs. It also advertises that it can send PR to a github project that correct issues and it can supposedly run checks on PRs. +[quantifiedcode](https://www.quantifiedcode.com/) is a tool that checks code for best practices and finds bugs. It also can send a PR to a github project to correct issues and it can run checks on PRs. We are discussing under issue [#583](/MDAnalysis/mdanalysis/issues/583) how to best use *quantifiedcode* with MDAnalysis. ## quantifiedcode: MDAnalysis ## It is now enabled for MDAnalysis: @@ -22,3 +22,5 @@ So, if you have a moment to spare, go to the URL above, pick something easy that As the issue title use the *SAME TITLE* as the QC issue (to avoid duplication). As example see https://github.com/MDAnalysis/mdanalysis/issues/564 --- assume that someone new to MDAnalysis will read the issue so be explicit and use links to the QC issue. + +If the issue has the magic "fix it" link enabled, you can also ask quantifiedcode to submit a PR. If this does not work, look at issue [#583](/MDAnalysis/mdanalysis/issues/583).