Migrate commit from ASH

.github/workflows/standard-workflow.yml

@@ -34,13 +34,13 @@ jobs:
         run: sbt scalafmtCheckAll scalafmtSbtCheck "scalafixAll --check"
         working-directory: examples/event-migration
 
-      - name: Check code style - examples/akka-cluster-app
+      - name: Check code style - examples/pekko-cluster-app
         run: sbt scalafmtCheckAll scalafmtSbtCheck "scalafixAll --check"
-        working-directory: examples/akka-cluster-app
+        working-directory: examples/pekko-cluster-app
 
-      - name: Check code style - examples/akka-persistence-app
+      - name: Check code style - examples/pekko-persistence-app
         run: sbt scalafmtCheckAll scalafmtSbtCheck "scalafixAll --check"
-        working-directory: examples/akka-persistence-app
+        working-directory: examples/pekko-persistence-app
 
   test-212:
     runs-on: ubuntu-latest
@@ -126,50 +126,14 @@ jobs:
         run: sbt test
         working-directory: examples/event-migration
 
-      - name: Compile akka-cluster-app
+      - name: Compile pekko-cluster-app
         run: sbt compile
-        working-directory: examples/akka-cluster-app
+        working-directory: examples/pekko-cluster-app
 
-      - name: Test akka-persistence-app
+      - name: Test pekko-persistence-app
         run: sbt test
-        working-directory: examples/akka-persistence-app
+        working-directory: examples/pekko-persistence-app
 
-  # <START-AKKA>
-  open-pr-to-ash:
-    if: github.event_name != 'pull_request'
-    needs: [code-style-check, test-212, test-213-1, test-213-2, test-sbt-plugin, run-examples]
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          # Fetch all history so that a push to pekko-serialization-helper succeeds.
-          # See https://stackoverflow.com/q/76470864
-          fetch-depth: 0
-      - uses: coursier/cache-action@v6
-      - uses: coursier/setup-action@v1
-      - run: git status
-      - run: git checkout -b chore/from-ash
-      - run: curl -sL https://raw.githubusercontent.com/ap/rename/master/rename | sudo tee /usr/local/bin/rename
-      - run: sudo chmod +x /usr/local/bin/rename
-      - run: ./scripts/akka-to-pekko
-      - run: git add .
-      - run: git config user.email "[email protected]"
-      - run: git config user.name "Pekko Serialization Helper Bot"
-      - run: git commit -m 'Migrate commit from ASH'
-      - run: git clean -dxf
-      - run: ./scripts/format-code
-      - run: git commit -a --amend --no-edit
-      - env:
-          # 2.1 Generate an SSH key in terminal (Leave the passphrase empty)
-          # 2.2 Add public key in the external repository: <external repository>/Settings/Deploy keys/Add deploy key
-          #     Paste the public key. Enable "Allow write access"
-          # 2.3 Add private key in the source repository: <external repository>/Settings/Secrets/Actions/New repository secret
-          #     Paste the private key.
-          PSH_SSH_PRIVATE_KEY: ${{ secrets.PSH_SSH_PRIVATE_KEY }}
-        run: mkdir -p ~/.ssh/ && echo "$PSH_SSH_PRIVATE_KEY" > ~/.ssh/psh && chmod 400 ~/.ssh/psh
-      - run: git config --add --local core.sshCommand 'ssh -i ~/.ssh/psh'
-      - run: git push --force [email protected]:VirtusLab/pekko-serialization-helper.git HEAD:main
-  # <END-AKKA>
 
   publish-maven-artifacts:
     needs: [code-style-check, test-212, test-213-1, test-213-2, test-sbt-plugin, run-examples]

.scalafix.conf

@@ -9,5 +9,5 @@ OrganizeImports.groups = [
   "java.",
   "scala.",
   "*",
-  "org.virtuslab.ash"
+  "org.virtuslab.psh"
 ]

CONTRIBUTING.md

@@ -28,16 +28,16 @@ and using it in another project. Make sure that `mavenLocal` is added to the res
 sbt publishM2
 ```
 
-You can find two example applications that use Akka Serialization Helper:
-- [akka-cluster-app](examples/akka-cluster-app)
-- [akka-persistence-app](examples/akka-persistence-app)
+You can find two example applications that use Pekko Serialization Helper:
+- [pekko-cluster-app](examples/pekko-cluster-app)
+- [pekko-persistence-app](examples/pekko-persistence-app)
 These apps can be used for basic runtime testing as well. First, go to the app's directory:
 ```shell
-cd examples/akka-cluster-app
+cd examples/pekko-cluster-app
 ```
 or
 ```shell
-cd examples/akka-persistence-app
+cd examples/pekko-persistence-app
 ```
 And follow instructions from their README files.
 
@@ -68,7 +68,7 @@ Otherwise, incremental compilation might determine there is nothing to compile a
 
 ### Profiling
 
-To profile akka-serialization-helper compiler plugin used in another project - follow instructions from https://www.lightbend.com/blog/profiling-jvm-applications
+To profile pekko-serialization-helper compiler plugin used in another project - follow instructions from https://www.lightbend.com/blog/profiling-jvm-applications
 You might as well use any other profiler, but using https://github.com/jvm-profiling-tools/async-profiler with flamegraphs should be really effective and easy to achieve (+ no unexpected bugs / issues / errors).
 
 ### Code quality
@@ -88,7 +88,7 @@ Releasing is done automatically by `sbt-ci-release` sbt plugin (read more on the
 
 ### Snapshots
 
-The new `SNAPSHOT` version is automatically published by GitHub Actions to [Sonatype OSS Snapshot repo](https://oss.sonatype.org/content/repositories/snapshots/org/virtuslab/ash/)
+The new `SNAPSHOT` version is automatically published by GitHub Actions to [Sonatype OSS Snapshot repo](https://oss.sonatype.org/content/repositories/snapshots/org/virtuslab/psh/)
 every time a new commit is pushed to `main`.
 
 To depend on the newest version with sbt, add the following setting:
@@ -99,7 +99,7 @@ to both `build.sbt` **and** `project/build.sbt` (so that the sbt plugin added in
 
 ### Maven Central
 
-Releases to [Maven Central](https://repo1.maven.org/maven2/org/virtuslab/ash/) are triggered by pushing a lightweight git tag with a version number.
+Releases to [Maven Central](https://repo1.maven.org/maven2/org/virtuslab/psh/) are triggered by pushing a lightweight git tag with a version number.
 
 To publish version x.y.z, type in the console (on main branch):
 ```shell