Skip to content

Docs update #502

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

Merged
merged 6 commits into from
Jul 16, 2015
Merged

Docs update #502

merged 6 commits into from
Jul 16, 2015

Conversation

JakeGinnivan
Copy link
Contributor

Ported wiki docs and wrote a bunch of new docs

@JakeGinnivan
Copy link
Contributor Author

@gep13 @robdmoore thoughts on the docs updates.

I like having them in the repo as people can PR. Later we can build a github.io page from that folder too. You can browse and have a read at https://github.com/JakeGinnivan/GitVersion/tree/DocsUpdate

@gep13
Copy link
Member

gep13 commented Jul 15, 2015

@JakeGinnivan so, does that mean we are not going to be using readme.io anymore?

@gep13
Copy link
Member

gep13 commented Jul 15, 2015

I have had a quick skim through this, but will need to dig into it deeper. From what I read, it looks good though! 👍

JakeGinnivan added a commit that referenced this pull request Jul 16, 2015
@JakeGinnivan JakeGinnivan merged commit dbc14d5 into GitTools:master Jul 16, 2015
@JakeGinnivan JakeGinnivan deleted the DocsUpdate branch July 16, 2015 01:28
@gep13
Copy link
Member

gep13 commented Jul 16, 2015

@JakeGinnivan did you see my question above? Cheers!

@JakeGinnivan
Copy link
Contributor Author

Ah yeah. I think for the moment not using readme.io.

Having docs outside the repo makes it hard to keep docs and pr's in sync. I also like having atom open just editing locally, it is easier than editing in the browser.

@JakeGinnivan
Copy link
Contributor Author

My ideal scenario is having a deployment step which would push the docs into a new readme.io version. Then you take advantage of the versioned docs and can just build docs during a release. Then somehow having a process for updating the docs as well outside a release

@gep13
Copy link
Member

gep13 commented Jul 16, 2015

@JakeGinnivan said...
My ideal scenario is having a deployment step which would push the docs into a new readme.io version. Then you take advantage of the versioned docs and can just build docs during a release. Then somehow having a process for updating the docs as well outside a release

Totally agree, this would be ideal!

@JakeGinnivan
Copy link
Contributor Author

Future Jake's problem :P

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