Skip to content

Fix genDoc script. Make sure main website is generated on snapshot. #8131

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 1 commit into from
Jan 30, 2020

Conversation

anatoliykmetyuk
Copy link
Contributor

When building a snapshot of the documentation, we must
also build the main website. Essentially this means generating
the same website twice, one time in the root directory,
the second time in the $version/ subdirectory of the root.

This is so because the contents of the github website will be
completely overwritten by the result of the genDocs command.
Hence, when the command is run with -doc-snapshot flag,
we must not only capture the doc snapshot but also generate the valid
website.

When building a snapshot of the documentation, we must
also build the main website. Essentially this means generating
the same website twice, one time in the root directory,
the second time in the $version/ subdirectory of the root.

This is so because the contents of the github website will be
completely overwritten by the result of the `genDocs` command.
Hence, when the command is run with `-doc-snapshot` flag,
we must not only capture the doc snapshot but also generate the valid
website.
Copy link
Member

@dottybot dottybot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello, and thank you for opening this PR! 🎉

All contributors have signed the CLA, thank you! ❤️

Commit Messages

We want to keep history, but for that to actually be useful we have
some rules on how to format our commit messages (relevant xkcd).

Please stick to these guidelines for commit messages:

  1. Separate subject from body with a blank line
  2. When fixing an issue, start your commit message with Fix #<ISSUE-NBR>:
  3. Limit the subject line to 72 characters
  4. Capitalize the subject line
  5. Do not end the subject line with a period
  6. Use the imperative mood in the subject line ("Add" instead of "Added")
  7. Wrap the body at 80 characters
  8. Use the body to explain what and why vs. how

adapted from https://chris.beams.io/posts/git-commit

Have an awesome day! ☀️

@nicolasstucki nicolasstucki merged commit 0b3627e into scala:master Jan 30, 2020
@nicolasstucki nicolasstucki deleted the doc-fix branch January 30, 2020 06:14
@nicolasstucki
Copy link
Contributor

@anatoliykmetyuk it still failed. I created https://github.com/lampepfl/dotty-website/tree/gh-pages/0.RC-dummy and restarted the CI test to see if that helps.

@nicolasstucki
Copy link
Contributor

@nicolasstucki
Copy link
Contributor

@anatoliykmetyuk it looks like we are adding an extra / at the front of the path
scala/dotty.epfl.ch@df0a001#diff-f3a36fbe5eab727e5dd72be075be267dR151

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.

3 participants