This is an automated email from the ASF dual-hosted git repository.

philippus pushed a change to branch 
allow-simpler-access-to-partition-assignment-strats
in repository https://gitbox.apache.org/repos/asf/pekko-connectors-kafka.git


    omit b5fb1582 Allow simpler access to partition assignment strategies
     add a4f3d52b only run nightly on main repo (#502)
     add a4a5a05b Update sbt-scalafmt to 2.6.0 (#503)
     add e103c2a9 Update scalafmt-core to 3.11.0 (#504)
     add 398b44f2 Retry committing for transient exceptions (#505)
     add e5193215 Allow simpler access to partition assignment strategies

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   (b5fb1582)
            \
             N -- N -- N   
refs/heads/allow-simpler-access-to-partition-assignment-strats (e5193215)

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/link-validator.yml               |   1 +
 .github/workflows/nightly-pekko.yml                |   2 +
 .scalafmt.conf                                     |   2 +-
 .../pekko/kafka/internal/KafkaConsumerActor.scala  |   9 +-
 docs/src/main/paradox/consumer.md                  | 244 +++++++--------------
 project/plugins.sbt                                |   2 +-
 .../kafka/internal/CommittingWithMockSpec.scala    |  14 +-
 7 files changed, 107 insertions(+), 167 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to