feat: implement log grouping for better output

README.md

@@ -29,8 +29,8 @@ and log out immediately after finishing their CI run, at which point they are au
 by the coordination server. The nodes are also [marked Preapproved][kb-auth-keys]
 on tailnets which use [Device Approval][kb-device-approval]
 
-
 ### Workload identity federation
+
 [Workload identity federation][kb-workload-identity-federation] can also be used for authenticating nodes with your tailnet:
 
 ```yaml
@@ -92,6 +92,27 @@ tailscale ping my-target.my-tailnet.ts.net
 
 The `ping` option will wait up to 3 minutes for a connection (direct or relayed).
 
+## Log mode
+
+By default, this action folds its major setup and cleanup phases into GitHub Actions log groups.
+You can change this with the `log-mode` input:
+
+```yaml
+- name: Tailscale
+  uses: tailscale/github-action@v4
+  with:
+    oauth-client-id: ${{ secrets.TS_OAUTH_CLIENT_ID }}
+    oauth-secret: ${{ secrets.TS_OAUTH_SECRET }}
+    tags: tag:ci
+    log-mode: normal
+```
+
+Supported values are:
+
+- `grouped`: fold major action phases in the log. This is the default.
+- `normal`: print routine action logs without grouping.
+- `quiet`: suppress routine informational output while preserving warnings and errors.
+
 ## Tailnet Lock
 
 If you are using this Action in a [Tailnet Lock][kb-tailnet-lock] enabled network, you need to:

action.yml

@@ -64,7 +64,11 @@ inputs:
     description: 'Comma separated list of hosts (Tailscale IP addresses or machine names if MagicDNS is enabled on the tailnet) to `tailscale ping` for connectivity verification after `tailscale up` completes.'
     required: false
     default: ''
-
+  log-mode:
+    description: 'Controls action log output mode. Use `grouped` to fold major setup and cleanup phases, `normal` for ungrouped logs, or `quiet` to suppress routine informational output.'
+    required: false
+    default: 'grouped'
+
 runs:
   using: 'node24'
   main: 'dist/index.js'