Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
info@openhub.net
Not sure why this would be failing.
See http://www.ohloh.net/p/htty/enlistments.
Thanks.
-- /\/. _/.
Nils:
It looks like either the GIT repository was rebased or some other forced commit (possibly retroactive) was applied.
This currently confuses ohloh and it stops getting updates.
I've started a re-fetch of the repository which will correct the problem and once it completes the project should be all set from then on :)
Is there anything I can do to recover from a failure like this? In the future, I mean. For example, deleting the enlistment and recreating it.
Thanks for the help.
Nils:
We want to make ohloh smarter about detecting that a GIT repository was rebased and automatically fix it by re-fetching.
Right now there is nothing your able to do in order to get it to recover.
We've talked about adding a link for you to trigger a re-fetch but there are some performance implications in adding that and we want to see if it's even still needed after we enhance ohloh to recover on it's own.