[Biopython-dev] Landscape.io & GitHub Fwd: Pull Request Status and Faster Checks

Peter Cock p.j.a.cock at googlemail.com
Fri Dec 4 10:18:36 UTC 2015

It looks like code quality checking and GitHub integration in general
is getting better all the time! Tiago setup landscape.io for us here:



---------- Forwarded message ----------
From: Carl from Landscape.io <carl at landscape.io>
Date: Fri, Dec 4, 2015 at 10:09 AM
Subject: Pull Request Status and Faster Checks
To: p.j.a.cock at googlemail.com

[image: Landscape] Landscape

Pull Request Status and Faster Checks

is a tool for checking your Python code and pointing out errors, problems
and stylistic issues. Think of it like an automatic code review. You are
receiving this email because you signed up for updates about new features.
You can unsubscribe
to stop receiving these emails.

Two updates for you this time: improvements to both pull request
integration with GitHub, and checks are now up to five times quicker.
Previously, Landscape would create a comment on pull requests
showing the change in code quality introduced by the proposed code. This
was often quite spammy, though, and therefore pull request status is now
set using GitHub's status API.

This means that, when you create a pull request, you will see something
like this:

The default behaviour is simply to add information about the code check to
the pull request. If you like, you can have Landscape mark the pull request
as "failed" if code quality deteriorates - you can do this in your
either for entire
organisations or on a per-repository basis.

Currently, failing can only be triggered by any decrease in score. If you
would like to have different criteria - for example, fail due to new errors
only but don't worry about smells - please file an issue on the issue
drop me an email
<carl at landscape.io?subject=Pull%20Request%20Status%20Criteria> so I can
figure out what kind of behaviour is useful!

The old commenting system is still available but has been disabled by
default in favour of the status updates. You can however enable it in your
It can still sometimes be useful if you tend to make pull requests then add
more commits afterwards, as with the status-api, it only represents the
most recent commit of the PR branch. The bot comments allow you to see how
new commits compare to old commits, if that history is useful to you.

This fixes issues #108
, #158

*Faster Checks*

The slowest part of the checks for some time has been setting up a virtual
environment and installing the various requirements of projects. This is
necessary to help with inferring types and APIs used by project code -
without the complete requirements, there are often several incorrect or
spurious warnings.

These requirements are now cached between checks. The first check will
still be slow as the environment is buit for the first time, but afterwards
the requirements installation is a lot faster, and will only need to fetch
and install libraries if the versions depended on have changed.

| Privacy
| Unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.open-bio.org/pipermail/biopython-dev/attachments/20151204/44159997/attachment-0001.html>

More information about the Biopython-dev mailing list