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.

Sign up for GitHub

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

Jump to bottom

Consider supporting a domain option that creates a custom CNAME #34

Closed
cvan opened this issue Dec 3, 2015 · 0 comments · Fixed by #533
Closed

Consider supporting a domain option that creates a custom CNAME #34

cvan opened this issue Dec 3, 2015 · 0 comments · Fixed by #533

Comments

@cvan
Copy link
Contributor

cvan commented Dec 3, 2015

I've run into conflicts where I had a CNAME checked into the repo, but I wanted to push the project to my fork, and it wouldn't work because you can't have two different repos sharing the same CNAME.

I've seen a couple similar gh-page deploy scripts do something similar. Here's one I found: https://github.com/nfroidure/buildbranch/blob/8d3cfd/src/index.js#L61-L64
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add --nojekyll and --cname options tschaub/gh-pages
1 participant
@cvan