Skip to content

Conversation

@BAOOOOOM
Copy link
Collaborator

Thanks for sending a pull request!
Please make sure you click the link above to view the contribution guidelines,
then fill out the blanks below.

Description

(Brief description on what this PR is about)

What does this implement/fix? Explain your changes.

  1. Update docs/source/conf.py
  2. Update docs/source/tutorial/zh/index.rst
  3. Update docs/source/tutorial/zh/parse.rst
  4. Update examples/Tokenizer/total_tokenize.ipynb
  5. Update examples/vectorization/total_vector.ipynb

Pull request type

  • [DATASET] Add a new dataset
  • [BUGFIX] Bugfix
  • [FEATURE] New feature (non-breaking change which adds functionality)
  • [BREAKING] Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • [STYLE] Code style update (formatting, renaming)
  • [REFACTOR] Refactoring (no functional changes, no api changes)
  • [BUILD] Build related changes
  • [DOC] Documentation content changes
  • [OTHER] Other (please describe):

Changes

  1. Update docs/source/conf.py
  2. Update docs/source/tutorial/zh/index.rst
  3. Update docs/source/tutorial/zh/parse.rst
  4. Update examples/Tokenizer/total_tokenize.ipynb
  5. Update examples/vectorization/total_vector.ipynb

Does this close any currently open issues?

#71

Any relevant logs, error output, etc?

N/A

Checklist

Before you submit a pull request, please make sure you have to following:

Essentials

  • PR's title starts with a category (e.g. [BUGFIX], [FEATURE], [BREAKING], [DOC], etc)
  • Changes are complete (i.e. I finished coding on this PR)
  • All changes have test coverage and al tests passing
  • Code is well-documented (extended the README / documentation, if necessary)
  • If this PR is your first one, add your name and github account to AUTHORS.md

Comments

  • If this change is a backward incompatible change, why must this change be made.
  • Interesting edge cases to note here

Copy link
Collaborator Author

@BAOOOOOM BAOOOOOM left a comment

Choose a reason for hiding this comment

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

checked

@codecov-commenter
Copy link

Codecov Report

Merging #93 (40d7d93) into docs (be85d71) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##              docs       #93   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           46        46           
  Lines         1365      1365           
=========================================
  Hits          1365      1365           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update be85d71...40d7d93. Read the comment docs.

@BAOOOOOM BAOOOOOM merged commit b7f3ff0 into bigdata-ustc:docs Sep 14, 2021
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