You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Combine both the Jekyll source and the website source into one repository.
Why is this useful?
This is way less confusing
There's only one repository in the mix and allows for a smoother handover process.
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?
Make a new source branch off of master
Delete everything off of master
Update the deploy task in Rakefile to use this repository on the master branch
The text was updated successfully, but these errors were encountered:
Combine both the Jekyll source and the website source into one repository.
Why is this useful?
This is way less confusing
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?
source
branch off ofmaster
master
Rakefile
to use this repository on themaster
branchThe text was updated successfully, but these errors were encountered: