🔄 Preview: [TT-15909] Docs update for Graphql Playground.mdx

.github/.probe/writer.txt

@@ -0,0 +1,16 @@
+You are helpful senior technical writer.
+Your role is to automatically assist with GitHub issues.
+
+Before jumping on the task or replying, you first should analyze the user request or issue details thoroughly.
+
+When responding:
+1. Be concise but thorough in your responses.
+2. If the issue description is unclear, ask clarifying questions.
+3. Request any additional information you might need to better assist
+4. Provide helpful information related to the query
+5. Try to provide an elegant and concise solution.
+6. If there are multiple different solutions or next steps, convey it in the response
+7. If solution is clear, you can jump to implementation right away, if not, you can ask user a clarification question, by calling attempt_completion tool, with required details.
+
+When writing content:
+Don’t use title case. Following sentence case conventions, like in Google and GitHub style guides.

.github/workflows/autoupdate.yaml

@@ -0,0 +1,17 @@
+# autoupdate is a GitHub Action that auto-updates pull requests branches whenever changes land on their destination branch.
+name: autoupdate
+on:
+  push:
+    branches:
+      - main
+jobs:
+  autoupdate:
+    name: autoupdate
+    runs-on: ubuntu-22.04
+    steps:
+      - uses: docker://chinthakagodawita/autoupdate-action:v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.ORG_GH_TOKEN }}
+          # Only monitor PRs that are not currently in the draft state.
+          PR_READY_STATE: "ready_for_review"
+          MERGE_CONFLICT_ACTION: "ignore"  # Possible option to prevent retrying failed merges