Refactor DatasetOrTimeSchedule timetable docs#37771
Merged
potiuk merged 5 commits intoapache:mainfrom Feb 29, 2024
Merged
Conversation
dirrao
reviewed
Feb 28, 2024
sunank200
approved these changes
Feb 28, 2024
Co-authored-by: Ankit Chaurasia <8670962+sunank200@users.noreply.github.com>
739a348 to
b16a9df
Compare
uranusjr
approved these changes
Feb 29, 2024
Member
|
docs/static check failures |
…ow into refactor-timetable-docs taking latest
Contributor
Author
resolved |
potiuk
approved these changes
Feb 29, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As we have changed timetable name from
DatasetTimetabletoDatasetOrTimeSchedule, looks like docs were not updated fixing that in this PR^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.