Using version eye on gh-pages

[Milan Raj]

I am trying to use version eye on github.com/rajsite/rajsite.com The repository only has one branch, the default, which is gh-pages

However when I go to https://www.versioneye.com/user/projects/github/rajsite/rajsite.com/show

and press "Update meta-data about this repository" no branches are shown.

I have some build scripts that run on Travis CI and it would be nice to know that my dependencies are up to date / secure.

[Milan Raj]

I was able to workaround by making multiple versioneye projects by URL (one for package.json and one for Gemfile)

[Robert Reiz]

I just forked your repo and could reproduce it.

[Robert Reiz]

@rajsite Branches with the name gh-pages are ignored. See here: https://github.com/versioneye/versioneye-core/blob/master/lib/versioneye/services_ext/github.rb#L161. Nor sure anymore why. I guess because gh-pages branches are not regular branches. You could create another branch develop and then merge into gh-pages every time you want to deploy and the develop could be monitored by VersionEye. What do you think?

[Milan Raj]

Realistically I probably won't change my workflow that drastically to support the service. Manually creating URLs pointing to the package.json / Gemfile in gh-pages seems like an almost okay workaround if documented in the FAQ. My guess is there is no fundamental issue because I was able to use the 3rd party gemnasium.com service fine by changing the monitored branch from master to gh-pages in their settings.

[Robert Reiz]

OK. I just removed the 2 lines which caused to ignore the gh-pages branch: https://github.com/versioneye/versioneye-core/commit/b50a7b60afc3d188fb84835a69f1d73fba4db56c. Please try again. It will work now.