Currently, our Python API code is a module in apache/dolphinscheduler codebase,
each time users change Python API code, they need to run all requests CI check
for dolphinscheduler and Python API, But if the user does only change Python
code, it could be merged if Python API CI pass and do not dependent on others CI.
Besides, we release Python API as the same version of dolphinscheduler. It is
easy for user to match Python API version. But when Python API does not change
any code, but dolphinscheduler release a bugfix version, Python API has to
release the new version to match dolphinscheduler. This happened when we
released Python API 2.0.6 and 2.0.7. 2.0.6 and 2.0.7 is bugfix version, and
Python API does not change any code, so the PyPI package is the same.
Separate Python API also makes our code more sense, we will have more
distinguished code in dolphinscheduler and Python API new repository.
Have separate issue tracker and changelog for information to users.
ref PR in other repository: apache/dolphinscheduler-sdk-python#1
see more detail in mail thread: https://lists.apache.org/thread/4z7l5l54c4d81smjlk1n8nq380p9f0oo
* try to fix ci
* try to fix ci
* try to fix ci
* try to fix ci
* try to fix ci
* try to fix ci
* try to fix ci
* try to fix ci
* try to fix ci
* try to fix ci
* try to fix ci
* try to fix ci
* try to fix ci
CI could not be run due to we add 9113817b to asf
configure and same file change will not trigger
build or unit test github actions run. This patch
try to skip github action path ignore rule temporarily
Maybe we should find more effective way to spearate py
, js, java CI later
* [python] Add code style lint for GA
* Change github action name
* Auto change by black
* Fix flake8
* Fix broken link for pyds README.md
* Auto fix by black
* Separate GitHub workflows
* Add Black badge and CI locally in README.md
Wenjun Ruan