This is an automated email from the ASF dual-hosted git repository.
fanningpj pushed a change to branch pjfanning-patch-2
in repository https://gitbox.apache.org/repos/asf/pekko-persistence-jdbc.git
omit 9c01eab change test
omit a75e314 Update DurableStateStorePluginSpec.scala
omit b73a718 Update MigrationScriptSpec.scala
omit 4a941f3 oracle migration
omit 5cf1b51 Make TAG column nullable in oracle-create-schema.sql
add 4d72aca Bump jrouly/scalafmt-native-action from 4 to 5 (#484)
add 1755383 Make TAG column nullable in oracle-create-schema.sql
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 (9c01eab)
\
N -- N -- N refs/heads/pjfanning-patch-2 (1755383)
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/format.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
