Skip to content

Migrate remaning commigs from scala3doc repo #10148

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 19 commits into from
Nov 3, 2020

Conversation

romanowski
Copy link
Contributor

No description provided.

BarkingBad and others added 16 commits November 2, 2020 16:34
ScalaCommentToContentConverter needed to be refactored to inherit from
DocTagToContentConverter (because our version of `buildContent` needs to always
be called first before the super version, otherwise nested tags aren't seen by
our implementation).
If #paneSearch is missing dokka's ReactJS crashes and doesn't generate the search button.
I run 'git diff master --stat --name-only | xargs -I {}  sed -i 's/[[:space:]]*$//g' {}' with some manual tweaks
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! ☀️

@abgruszecki
Copy link
Contributor

@romanowski can also we fix the indentation to always be 2 spaces instead of sometimes 2, sometimes 4?

Copy link
Contributor

@abgruszecki abgruszecki left a comment

Choose a reason for hiding this comment

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

Everything LGTM, as far as I can tell.

I rendered the documentation locally and everything looked good as well.

@abgruszecki
Copy link
Contributor

OK, I think we can merge this, just to avoid conflicts piling up. If there are any remaining issues, we can fix them afterwards.

@bishabosha
Copy link
Member

merging because it only affects the scala3doc code

@bishabosha bishabosha merged commit e080d00 into scala:master Nov 3, 2020
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.

7 participants