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

Combine repositories to one #3

Open
andrewjkerr opened this issue Sep 1, 2016 · 0 comments
Open

Combine repositories to one #3

andrewjkerr opened this issue Sep 1, 2016 · 0 comments
Assignees

Comments

@andrewjkerr
Copy link
Member

andrewjkerr commented Sep 1, 2016

Combine both the Jekyll source and the website source into one repository.

Why is this useful?

This is way less confusing

  1. There's only one repository in the mix and allows for a smoother handover process.
  2. We can use the Wiki to document how the site works more than just some simple instructions in the repository.

One less private repository

It's kinda weird that our website code is public, but the Jekyll code isn't. We could publish this code, but there's really no reason to have it public. By combining the repositories, we will have both the website source and the Jekyll source in one private repo and not have to worry about it anymore!

How will this work?

  1. Make a new source branch off of master
  2. Delete everything off of master
  3. Update the deploy task in Rakefile to use this repository on the master branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant