This is an automated email from the ASF dual-hosted git repository.
vatsrahul1001 pushed a change to branch backport-881f362-v3-4-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit 5d3aac86b05 [v3-4-test] Run the flynt prek hook in parallel batches
(#75274) (cherry picked from commit 881f36223045f8e545c2b2ae1f08ed29662beedc)
add fd417e212b0 [v3-4-test] Raise the stale bot operation budget so it
reaches older PRs (#75761) (#75794)
add 029a18c56e0 [v3-4-test] Run the flynt prek hook in parallel batches
(#75274) (cherry picked from commit 881f36223045f8e545c2b2ae1f08ed29662beedc)
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (5d3aac86b05)
\
N -- N -- N refs/heads/backport-881f362-v3-4-test (029a18c56e0)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.github/workflows/stale.yml | 1 +
1 file changed, 1 insertion(+)
