-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status broken after domain change #14
Comments
This is fixed as of Thu Jan 17 20:47:13 PST 2013 |
P.S. The fix above was to configure the HOST environment variable on Heroku. Then I retroactively updated all webhook URLs on your repos with I realized I also needed to re-check all open Pull Requests, so I have now also done that with: Hopefully all is now well. |
So, as of Thu Jan 17 20:51:35 PST 2013 |
Pulls which are good to merge should look like: jasonm/clahub-test2#1 |
When changing domains from clahub.herokuapp.com to www.clahub.com, I neglected to update a production config variable that determines the hostname for GitHub's post-receive webhook notifications. As such, commits were not being updated as pass/fail based on CLA signature status.
This has been fixed and I updated all existing webhook URLs via API in production and verified this.
For folks with CLAs on the production site: I'd generally avoid publicizing user information, but I'd rather notify folks about this. I've emailed everyone whose email I can ascertain. For others I only have the GitHub username, and can't figure out how to send a GH message (didn't that feature exist previously?) As such, cc @maxandersen @webmink @pidster.
The text was updated successfully, but these errors were encountered: