show build status of current branch

And lots of other error handling so you don't have to open the console.
Hmm.  Actually it's not the Circle CI API limit I'm concerned about, it's the constant background polling even if no projects are open that are in Circle.  I know that a few polls don't seem like much on their own, but if every plugin was doing the same thing it wouldn't be long before Atom got real slow.

In which case I wonder if it's worth us checking to see whether the project is in Circle CI if the branch fails.  If it's not there, then reduce the polling to longer intervals.  If the branch isn't there, but the project is - then keep polling at normal speed.  That's what I'm doing in the refactor.

That said though, this is really only a temporary solution since I am in the process of refactoring a lot of this stuff as I said - so perhaps it's OK for now.