Check for leftover examples to integrate
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
### Description
As described in https://cwiki.apache.org/confluence/display/AIRFLOW/Examples+Refurbish
Once all examples are migrated, check for leftover simple examples and check if they can be integrated into the storyline to reduce.
This includes:
- Dag is adjusted in Taskflow as well as classic implementation
- Dag is according to checklist
- Previous examples that are content-wise replaced are deleted to incrementally clean-up
- Airflow documentation is adjusted to point to new examples are replaced
- General example storyline overview is adjusted and the functioning of the new example is described
### Use case/motivation
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
Contributor guide
Research direction
Start with the Examples Refurbish page linked in the issue, then inventory the remaining Airflow examples and their documentation references. Compare them with the stated checklist and storyline, and consider the work done when eligible examples are integrated or removed, DAG variants and documentation are aligned, and the overview describes the functioning new example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100