Skip to content

Conversation

aayushbisen
Copy link
Contributor

@aayushbisen aayushbisen commented Jul 30, 2025

In the page https://airflow.apache.org/docs/apache-airflow/3.0.3/core-concepts/overview.html of the documentation in the images replaced the labels from "Webserver(s)" to "API Server(s)" in multiple diagrams.

Closes #53818


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

Copy link

boring-cyborg bot commented Jul 30, 2025

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

  • Pay attention to the quality of your code (ruff, 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.
  • Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
    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

@potiuk potiuk added the backport-to-v3-0-test Mark PR with this label to backport to v3-0-test branch label Jul 30, 2025
@vincbeck vincbeck merged commit 9383b0c into apache:main Jul 30, 2025
57 checks passed
Copy link

boring-cyborg bot commented Jul 30, 2025

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

Copy link

Backport failed to create: v3-0-test. View the failure log Run details

Status Branch Result
v3-0-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 9383b0c v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

RoyLee1224 pushed a commit to RoyLee1224/airflow that referenced this pull request Jul 31, 2025
potiuk pushed a commit to potiuk/airflow that referenced this pull request Aug 1, 2025
potiuk added a commit that referenced this pull request Aug 1, 2025
…n architecture diagrams (#53917) (#54020)

(cherry picked from commit 9383b0c)

Co-authored-by: Aayush Bisen <[email protected]>
ferruzzi pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request Aug 7, 2025
fweilun pushed a commit to fweilun/airflow that referenced this pull request Aug 11, 2025
@aayushbisen aayushbisen deleted the webserver-image-fix branch August 17, 2025 10:54
@aayushbisen aayushbisen restored the webserver-image-fix branch August 17, 2025 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-to-v3-0-test Mark PR with this label to backport to v3-0-test branch kind:documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Documents might need to update with AI server instead of webserver in some pages
4 participants