Skip to content
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

[DC 2016] add JHC Technology to sponsors #2770

Merged
merged 1 commit into from
May 3, 2016

Conversation

mcornick
Copy link
Contributor

@mcornick mcornick commented May 3, 2016

No description provided.

@bridgetkromhout
Copy link
Collaborator

Please submit a matching PR to https://github.com/devopsdays/devopsdays-web/pulls - thanks.

@mcornick
Copy link
Contributor Author

mcornick commented May 3, 2016

Will do - should future PRs go to that repo only, or both?

On May 3, 2016, at 3:27 PM, Bridget Kromhout notifications@github.com wrote:

Please submit a matching PR to https://github.com/devopsdays/devopsdays-web/pulls - thanks.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

@bridgetkromhout
Copy link
Collaborator

We're cutting over at the end of this week. If you can migrate your own site then it will be the way you want it. :)

@bridgetkromhout bridgetkromhout merged commit 3aca8e8 into jedi4ever:master May 3, 2016
@mcornick mcornick deleted the sponsor-jhc branch May 3, 2016 21:36
@mcornick
Copy link
Contributor Author

mcornick commented May 3, 2016

Thanks. I'm working on the migration to the new site in https://github.com/devopsdaysdc/devopsdays-web/tree/dc-2016-migration. It looks like we have some Very Special Blossom issues to figure out...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants