Skip to content

Conversation

@chicco785
Copy link
Contributor

Proposed changes

Revise docs

Types of changes

What types of changes does your code introduce to the project: Put
an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing
    functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to
ask. We're here to help! This is simply a reminder of what we are going
to look for before merging your code.

  • I have read the CONTRIBUTING doc
  • I have signed the Contributor License Agreement
  • I have updated the RELEASE NOTES
  • I have added tests that prove my fix is effective or that my
    feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in
    downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion
by explaining why you chose the solution you did and what alternatives
you considered, etc...

@github-actions
Copy link
Contributor

github-actions bot commented Oct 27, 2022

CLA Assistant Lite bot All contributors have signed the CLA ✍️

@chicco785 chicco785 requested a review from Cerfoglg October 30, 2022 14:57
@chicco785 chicco785 merged commit 80685c1 into master Oct 31, 2022
@chicco785 chicco785 deleted the revise-docs branch October 31, 2022 20:32
@github-actions github-actions bot locked and limited conversation to collaborators Oct 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants