Remove stale dag_ parameter from create_test_pipeline docstring#68787
Open
KenanAdel-M wants to merge 1 commit into
Open
Remove stale dag_ parameter from create_test_pipeline docstring#68787KenanAdel-M wants to merge 1 commit into
dag_ parameter from create_test_pipeline docstring#68787KenanAdel-M wants to merge 1 commit into
Conversation
|
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
|
c23dc11 to
bd22d2c
Compare
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
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.
Description
Remove a stale
:param DAG dag_:docstring entry from thecreate_test_pipelinefunction inexample_skip_dag.py.The parameter is not present in the function signature and is not used anywhere in the code or call sites.
This change aligns the documentation with the actual implementation.
No functional changes are introduced.
Change Type
Was generative AI tooling used to co-author this PR? No