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/master/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, pylint 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.
• 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://apache-airflow-slack.herokuapp.com/

Codecov Report

Merging #8276 into master will increase coverage by 0.72%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #8276      +/-   ##
==========================================
+ Coverage   86.92%   87.64%   +0.72%     
==========================================
  Files         920      937      +17     
  Lines       44387    45238     +851     
==========================================
+ Hits        38582    39651    +1069     
+ Misses       5805     5587     -218     

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b118916...ab1a5b9. Read the comment docs.

Hi. Thank you for the guide, but could you put each operator in a separate section / subsection. This is important because it makes it much easier to find the information you need.

Here ie example of guide with many section ("Managing an entries"), and subsection ("Creating an entries")

@mik-laj I added subtitles for each operator except BigQueryExecuteQueryOperator as that is the only operator discussed in the section "Execute queries".

One more thing. Can you add this guide to the operators reference?
https://github.com/apache/airflow/blob/master/docs/operators-and-hooks-ref.rst
https://airflow.readthedocs.io/en/latest/operators-and-hooks-ref.html

I added the bigquery howto to operators-and-hooks-ref.rst

Yay! I work a lot with Airflow on GCP so I'll probably contribute more around that :)

Airflow has a very active GCP user community. For sure you won't run out of tasks. 😸 I will try to regularly create new tickets with the "provider: GCP" label

Awesome work, congrats on your first merged pull request!