As stated here, there are cases where the user is on a pull request page but BitShip is not running.
This happens when navigating to any of the Overview, Commits or Activity tabs in the PR page. The tabs modify the url and add another parameter that messes up with the url pattern matching in the extension manifest.
This is related to, but shouldn't be part of #16.
The extension shouldn't be always active. Even though it is only actually running on bitbucket pull request pages, the icon shouldn't be visible if you're not on that page
After a pull request is merged, there is a new commit - a merge commit - that has the same codebase, but shuold be tested again.
Currently the codeship badge lists the result of the build of the original commit.
ideas?
It would be great if the extension could add some sort of UI notification to the pull-requests page too. This way you could easily have an overview of the build statuses of all your pull requests
After a pull request has just been created, the codeship badge is gray and shows that the build is in progress. If the build has finished, you have to manuall yrefresh the page in order to chec the status badge.
I think that the plugin itself should either listen to some codeship api callback or either be polling for build status updates to keep the user up to date about the pull request status.