-
-
Notifications
You must be signed in to change notification settings - Fork 598
Docs releases #522
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
Docs releases #522
Conversation
- Adds CloudCode.js file - Updates travis.yaml for releases - Adds release script
Codecov Report
@@ Coverage Diff @@
## master #522 +/- ##
=======================================
Coverage 84.59% 84.59%
=======================================
Files 48 48
Lines 3952 3952
Branches 897 897
=======================================
Hits 3343 3343
Misses 609 609 Continue to review full report at Codecov.
|
local_dir: docs/ | ||
on: | ||
all_branches: true | ||
- provider: npm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Me Gusta! Awesome that this would cut out a step we would have to do by hand 👍 .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes! Figured we should do as much as we could!
then | ||
DEST="${TRAVIS_TAG}" | ||
# change the default page to the latest | ||
echo "<meta http-equiv='refresh' content='0; url=/Parse-SDK-JS/api/${DEST}'>" > "docs/api/index.html" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is interesting... So per release we're just redirecting via meta to the latest set? That's kind of cool actually. One thing I'm curious about is if we're maintaining an index or a table of contents for existing doc versions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So far we don’t, but with this strategy we’ll be able to :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. I'll defer to the results of the CI.
Ci passes! Once merged this should put the master doc set in gh pages, I did extensive testing on my repo :) https://travis-ci.org/flovilmart/Parse-SDK-JS/branches |
Now that's a sight to see 🍻 . |
Took a few weekends to get there, next is all iOS repos! We can later customize the theme/template if we have time, to make it more parse-like . There's docstrap that offers a nice template, more customizable, and with more fluid navigation. |
gh-pages
with preservation of current branch.