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 Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it’s a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

I am now beginning to get what i need to do in the docs. thanks for the breakdown

Do you mind if you can assist me on that issue?

Sure. The goal is to explain the users how to setup the classes in https://github.com/apache/airflow/blob/main/airflow/providers/apache/pinot/hooks/pinot.py
explain about the parameters / diffrent configurations / tips / anything else that worth mentioning.
You can create example dags and incorporate it into the guide.
You can look up our documentation for guides that we have on other operators/hook.

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.

Was the =2.1.0 file accidentally committed?

Was the =2.1.0 file accidentally committed?

I wen't ahead and deleted it via Github UI :). Nice catch @uranusjr

I think there are unrelated changes in that PR.
Why there are changes to airflow/_vendor/connexion/ ?

Why there are changes to airflow/_vendor/connexion/ ?

Indeed - should be removed.

It seems like the merge (or rebase?) didn't went well and pulled in a ton of unrelated things...

I have rebased it but I still dont get why it is still pushing with the unrelated changes

I think this is rebased to the wrong base. Not sure what the best way to recover is; personally I usually cherry-pick the commits manually back:

# Assumes 'origin' points to apache/airflow -- adjust 'origin' as needed.
git fetch origin main
git branch -f main origin/main  # Point the local 'main' to the origin's main.
git checkout main
git cherry-pick e700a59ae85beb7bbfbd25153b4d9eeb3c78a9d8  # Manully apply the commit's changes again.
git push --force

To avoid this from happening again, it is best to avoid making changes on your own 'main' directly, but instead create a branch for each pull request. Since this PR is already submitted, it is not possible to change the originating branch now, but this is a good approach to remember if you plan to make other pull requests in the future.

@sharon2719 There are still many unrelated changes in the branch (lower than before tough) please remove all unrelated code changes you can see in https://github.com/apache/airflow/pull/18930/files the files that you are modifying

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.