Update Learning Hub: /fork naming, gh auto-approval, --resume cloud agent (#1704)

- copilot-configuration-basics.md: document /fork with optional name (v1.0.47),
  origin display in sessions dialog, and read-only gh CLI auto-approval (v1.0.46)
- using-copilot-coding-agent.md: document --resume support for cloud agent
  sessions with no pushed changes (v1.0.47)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

website/src/content/docs/learning-hub/copilot-configuration-basics.md

@@ -3,7 +3,7 @@ title: 'Copilot Configuration Basics'
 description: 'Learn how to configure GitHub Copilot at user, workspace, and repository levels to optimize your AI-assisted development experience.'
 authors:
   - GitHub Copilot Learning Hub Team
-lastUpdated: 2026-05-11
+lastUpdated: 2026-05-13
 estimatedReadingTime: '10 minutes'
 tags:
   - configuration
@@ -468,10 +468,11 @@ Use `/undo` when the agent's last response went in an unwanted direction and you
 The `/fork` command (v1.0.45+) copies the current session into a **new independent session** that starts from the same conversation state. The original session continues unchanged — you can switch back to it at any time. This is useful when you want to explore two different approaches to a problem simultaneously:
 
 ```
-/fork
+/fork                    # fork with an auto-generated name
+/fork "my-experiment"    # fork with a custom name (v1.0.47+)
 ```
 
-After forking, the new session is immediately active. Both sessions share the same history up to the fork point but accumulate changes independently from that moment forward. Use `/fork` to experiment with a risky refactor without abandoning your current working session.
+After forking, the new session is immediately active. Both sessions share the same history up to the fork point but accumulate changes independently from that moment forward. Use `/fork` to experiment with a risky refactor without abandoning your current working session. Since v1.0.47, forked sessions display their **origin session** name in the sessions dialog, making it easy to trace which session a fork came from.
 
 The `/cd` command changes the working directory for the current session. Each session maintains its own working directory that persists when you switch between sessions:
 
@@ -573,6 +574,8 @@ The `/autopilot` command (v1.0.45+) is a quick in-session toggle that switches b
 
 Use `/autopilot` when you want to flip between supervised and unsupervised operation mid-session without typing out the full `/allow-all on` or `/allow-all off` commands.
 
+> **Read-only `gh` CLI commands (v1.0.46+)**: Read-only `gh` commands — such as `gh issue list`, `gh pr view`, `gh run status`, and other commands that don't write to GitHub — are **automatically approved** without a permission prompt. Only commands that write to GitHub (like creating issues, merging PRs) still require explicit approval. This reduces friction during exploratory sessions where you frequently check issue or PR status.
+
 The `--effort` flag (shorthand for `--reasoning-effort`) controls how much computational reasoning the model applies to a request:
 
 ```bash

website/src/content/docs/learning-hub/using-copilot-coding-agent.md

@@ -3,7 +3,7 @@ title: 'Using the Copilot Coding Agent'
 description: 'Learn how to use GitHub Copilot coding agent to autonomously work on issues, generate pull requests, and automate development tasks.'
 authors:
   - GitHub Copilot Learning Hub Team
-lastUpdated: 2026-04-28
+lastUpdated: 2026-05-13
 estimatedReadingTime: '12 minutes'
 tags:
   - coding-agent
@@ -364,6 +364,8 @@ Remote sessions also appear in the `--resume` picker, so you can reconnect to a
 copilot --resume
 ```
 
+Since v1.0.47, `--resume` also surfaces **cloud agent sessions that haven't yet pushed any changes** to their branch — useful for connecting to a session early in its run, before it has committed anything.
+
 ### Why Use Remote Control?
 
 | Scenario | Benefit |