This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 41815d98f24 Fixing some nits in 01_ci_environment.md (#45277)
41815d98f24 is described below
commit 41815d98f2405df60a6d61a4558409a3badbafd3
Author: Amogh Desai <[email protected]>
AuthorDate: Mon Dec 30 13:27:39 2024 +0530
Fixing some nits in 01_ci_environment.md (#45277)
---
dev/breeze/doc/ci/01_ci_environment.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev/breeze/doc/ci/01_ci_environment.md
b/dev/breeze/doc/ci/01_ci_environment.md
index c1cc51c3254..21044af5141 100644
--- a/dev/breeze/doc/ci/01_ci_environment.md
+++ b/dev/breeze/doc/ci/01_ci_environment.md
@@ -33,7 +33,7 @@
Continuous Integration is an important component of making Apache Airflow
robust and stable. We run a lot of tests for every pull request,
-for `canary` runs (from `main` and `v*-\*-test` branches and
+for `canary` runs from `main` and `v*-\*-test` branches
regularly as scheduled jobs.
Our execution environment for CI is [GitHub
Actions](https://github.com/features/actions). GitHub Actions.
@@ -87,7 +87,7 @@ merging the manifests, and it is not really needed nor used
for cache.
Authentication to GitHub Registry in CI uses GITHUB_TOKEN mechanism.
The Authentication is needed for pushing the images (WRITE) in the `canary`
runs.
-When you are running the CI jobs in GitHub Actions, vGITHUB_TOKEN is set
automatically
+When you are running the CI jobs in GitHub Actions, GITHUB_TOKEN is set
automatically
by the actions. This is used only in the `canary` runs that have "write" access
to the repository.
