Skip to content
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] - Update Schedule API docs (DOC-236) #21838

Merged
merged 30 commits into from
May 23, 2024

Conversation

erinkcochran87
Copy link
Contributor

@erinkcochran87 erinkcochran87 commented May 14, 2024

Summary & Motivation

This PR updates the Schedule API docs by adding information to the reference page itself as well as some of the API descriptions.

How I Tested These Changes

eyes + local, ruff + BK

@graphite-app graphite-app bot added the area: docs Related to documentation in general label May 14, 2024
@erinkcochran87 erinkcochran87 changed the title Erin/doc 236 api schedule [docs] - Update Schedule API docs (DOC-236) May 14, 2024
Copy link
Contributor

@tacastillo tacastillo left a comment

Choose a reason for hiding this comment

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

Generally looks good to me, but looks like there was a rough merge that accidentally pulled in some old (or new?) changes in some of the actual codebase! Feel free to hit re-review when that merge is fixed.

Also left a couple comments to hone in on some edges.

Copy link
Contributor

@tacastillo tacastillo left a comment

Choose a reason for hiding this comment

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

LGTM! thanks for dealing with git hell.

@erinkcochran87 erinkcochran87 merged commit 128f30e into master May 23, 2024
1 of 2 checks passed
@erinkcochran87 erinkcochran87 deleted the erin/doc-236-api-schedule branch May 23, 2024 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: docs Related to documentation in general
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants