Only build for main branches to fix duplicate actions with dependabot

Author: games647

.github/workflows/maven.yml

@@ -4,11 +4,15 @@
 # Human readable name in the actions tab
 name: Java CI
 
-# Build on every push and pull request regardless of the branch
+# Build on every pull request regardless of the branch
 # Wiki: https://help.github.com/en/actions/reference/events-that-trigger-workflows
 on:
-    - push
-    - pull_request
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
 
 jobs:
   # job id
@@ -19,32 +23,32 @@ jobs:
 
     # Run steps
     steps:
-    # Pull changes
-    - uses: actions/[email protected]
-
-    # Cache artifacts - however this has the downside that we don't get notified of
-    # artifact resolution failures like invalid repository
-    # Nevertheless the repositories should be more stable and it makes no sense to pull
-    # a same version every time
-    # A dry run would make more sense
-    - uses: actions/[email protected]
-      with:
-        path: ~/.m2/repository
-        key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
-        restore-keys: |
-          ${{ runner.os }}-maven-
-
-    # Setup Java
-    - name: Set up JDK
-      uses: actions/[email protected]
-      with:
-        distribution: 'adopt'
-        # Use Java 11, because it's minimum required version
-        java-version: 11
-
-    # Build and test (included in package)
-    - name: Build with Maven and test
-    # Run non-interactive, package (with compile+test),
-    # ignore snapshot updates, because they are likely to have breaking changes, enforce checksums to validate
-    # possible errors in dependencies
-      run: mvn test --batch-mode --no-snapshot-updates --strict-checksums --file pom.xml
+      # Pull changes
+      - uses: actions/[email protected]
+
+      # Cache artifacts - however this has the downside that we don't get notified of
+      # artifact resolution failures like invalid repository
+      # Nevertheless the repositories should be more stable and it makes no sense to pull
+      # a same version every time
+      # A dry run would make more sense
+      - uses: actions/[email protected]
+        with:
+          path: ~/.m2/repository
+          key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
+          restore-keys: |
+            ${{ runner.os }}-maven-
+
+      # Setup Java
+      - name: Set up JDK
+        uses: actions/[email protected]
+        with:
+          distribution: 'adopt'
+          # Use Java 11, because it's minimum required version
+          java-version: 11
+
+      # Build and test (included in package)
+      - name: Build with Maven and test
+        # Run non-interactive, package (with compile+test),
+        # ignore snapshot updates, because they are likely to have breaking changes, enforce checksums to validate
+        # possible errors in dependencies
+        run: mvn test --batch-mode --no-snapshot-updates --strict-checksums --file pom.xml

bukkit/src/main/java/com/github/games647/fastlogin/bukkit/listener/protocollib/NameCheckTask.java

@@ -74,7 +74,8 @@ public void run() {
     }
 
     @Override
-    public FastLoginPreLoginEvent callFastLoginPreLoginEvent(String username, ProtocolLibLoginSource source, StoredProfile profile) {
+    public FastLoginPreLoginEvent callFastLoginPreLoginEvent(String username, ProtocolLibLoginSource source,
+                                                             StoredProfile profile) {
         BukkitFastLoginPreLoginEvent event = new BukkitFastLoginPreLoginEvent(username, source, profile);
         plugin.getServer().getPluginManager().callEvent(event);
         return event;