Rework repo to be mkdocs source project #11
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This repository was meant to be our deployment area, but turned into a development area. The deployment files need to be removed, then the repository renamed with a new one created at the github.io location.
tim-schilling
force-pushed
the
rework-repo-for-source
branch
from
4331c95 to
ccc09a9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This repository was meant to be our deployment area, but turned into a development area. The deployment files need to be removed, then the repository renamed with a new one created at the github.io location.
https://github.com/django-commons/django-commons-mkdocs/ was meant to be our source repo. I'm going to delete that, rename django-commons.github.io to django-commons-mkdocs and then recreate this repo. That will transition all of our issues and history over.
@williln since this is going to be a bit messy, I'm going to merge all these PRs and get this done sooner rather than later. I apologize for requesting reviews and then merging them without waiting.