Skip to content

Allow Hussein Awala to publish provider docs to S3 - #71848

Merged
hussein-awala merged 1 commit into
apache:mainfrom
hussein-awala:docs-publish-allowlist-hussein-awala
Aug 19, 2026
Merged

Allow Hussein Awala to publish provider docs to S3#71848
hussein-awala merged 1 commit into
apache:mainfrom
hussein-awala:docs-publish-allowlist-hussein-awala

Conversation

@hussein-awala

Copy link
Copy Markdown
Member

Add hussein-awala to the dispatcher allowlist in publish-docs-to-s3.yml.

The workflow gates its build-info job on github.event.sender.login, and every other job
depends on build-info — so when a committer outside the list dispatches it, the run is
created but every job is skipped. There is no error, which makes it easy to mistake for a
successful publish.

Hit while publishing staging docs for the 2026-08-18 provider wave (#71794): the dispatch
returned no error, the run appeared, and all six jobs reported skipped.

Note this does not affect dispatches against an already-cut release tag, since the allowlist
is read from the workflow file at the dispatched ref.


Was generative AI tooling used to co-author this PR?
  • Yes — Claude Code (Opus 5)

Generated-by: Claude Code (Opus 5) following the guidelines

@hussein-awala
hussein-awala merged commit 9c8d751 into apache:main Aug 19, 2026
63 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-3-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 9c8d751 v3-3-test

This should apply the commit to the v3-3-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

If you don't have cherry-picker installed, see the installation guide.

@eladkal eladkal removed the backport-to-v3-3-test Backport to v3-3-test label Aug 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants