improve premium requests lesson#18
Conversation
There was a problem hiding this comment.
Pull request overview
This PR simplifies the premium requests lesson (Lesson 19) by removing the "Premium request SKUs" subsection and replacing a reflective exercise prompt with an actionable /usage command reference.
Changes:
- Removed the "Premium request SKUs" table that distinguished between "Copilot premium requests" and "Copilot coding agent premium requests" SKUs.
- Updated exercise step 3 to direct users to run
/usageinstead of estimating their usage, making the exercise more concrete.
| @@ -43,15 +43,6 @@ Your plan includes a fixed number of premium requests per user per month. They r | |||
|
|
|||
| Once your allowance runs out, you can still use Copilot with the included models for the rest of the month. **Organisations can enable overage**, so if you exceed your allowance, additional premium requests will be billed per use rather than blocked. | |||
There was a problem hiding this comment.
Removing the "Premium request SKUs" table creates an orphaned reference: line 52 still says "show premium requests by user and SKU" but the SKUs are no longer defined anywhere in this lesson. Consider either updating line 52 to remove the "and SKU" reference, or retaining a brief inline explanation of the two SKU categories.
| 2. Run `/model` to browse available models and look up their multipliers at [Requests in GitHub Copilot — Model multipliers](https://docs.github.com/en/copilot/concepts/billing/copilot-requests#model-multipliers). | ||
| 3. Reflect on your usage patterns from this tutorial: | ||
| - Each prompt in Copilot CLI drew from your allowance if you were using a premium model — roughly how many did you use? | ||
| - Each prompt in Copilot CLI drew from your allowance if you were using a premium model — run `/usage` to see exactly how many premium requests you've used. |
There was a problem hiding this comment.
The /usage command (as described in Lesson 14) shows session-level statistics — request counts and token usage for the current session. The new wording "run /usage to see exactly how many premium requests you've used" implies it shows your overall account-level premium request consumption, which is misleading. /usage would only reflect requests made in the current CLI session, not your total monthly allowance consumption across all tools (IDE, code review, coding agent, etc.).
Consider clarifying this, e.g., "run /usage to see how many requests you've made in this session" and direct them to the Copilot settings page (already mentioned in step 1) for their full account-level premium request usage.
| - Each prompt in Copilot CLI drew from your allowance if you were using a premium model — run `/usage` to see exactly how many premium requests you've used. | |
| - Each prompt in Copilot CLI drew from your allowance if you were using a premium model — in this CLI session, run `/usage` to see how many requests you've made; for your full monthly premium usage, use your Copilot settings page. |
No description provided.