gion / bitship Goto Github PK

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.

If a build is queued, it isn't in progress, failing or successful. It's waiting.
We should implement a new ui/message for this status

Repro:

• create a branch with a # character in the name.
• create a pull request
• it shows the 'Branch not found' badge

Maybe this extension should also have a browser action view so that it can be easily accessed by the user

This issue is a hack in order to upload images that should be used in the readme file

Add google analytics for better flow usage understanding

It worked for a couple of weeks and now it does not anymore.

It does not show the badge in any project.

I know these information are not enough but I have no idea on how to debug and send more informations.

Just ask and I'll help fixing the issue.

I double-checked the api-key and is correct

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

It would be nice to have some sort of settings that can disable or temporary disable this extension on certain repos or branches

There should be some sort of way to alert the user if he didn't add the api key

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

Maybe the UI notice should be moved outside the tabbed content so that a user that navigates across any tab can see the UI notice:

User doesn't know if the api key is saved or not.

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.