Fix model name not found with gh models commands

[mgiovani]

Why:

This PR updates the documentation for the gh models run command to use a valid model name.
Previously, the docs referenced gpt-4.1, which is not a recognized model name and results in an error.
The example has been updated to use openai/gpt-4.1, which is a valid model name according to the CLI help and available models.

Closes: #38606

Screenshots:

• Before:
  

• After:
  

Code snippet changed:

-* **To ask a model a single question**, run `gh models run MODEL-NAME "QUESTION"` in your terminal. For example, to ask the {% data variables.copilot.copilot_gpt_41 %} model why the sky is blue, you can run `gh models run gpt-4.1 "why is the sky blue?"`.
+* **To ask a model a single question**, run `gh models run MODEL-NAME "QUESTION"` in your terminal. For example, to ask the {% data variables.copilot.copilot_gpt_41 %} model why the sky is blue, you can run `gh models run openai/gpt-4.1 "why is the sky blue?"`.

-* **To provide the output of a command as context when you call a model**, you can join a separate command and the call to the model with the pipe character (`|`). For example, to summarize the README file in the current directory using the {% data variables.copilot.copilot_gpt_41 %} model, you can run `cat README.md | gh models run gpt-4.1 "summarize this text"`.
+* **To provide the output of a command as context when you call a model**, you can join a separate command and the call to the model with the pipe character (`|`). For example, to summarize the README file in the current directory using the {% data variables.copilot.copilot_gpt_41 %} model, you can run `cat README.md | gh models run openai/gpt-4.1 "summarize this text"`.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[Copilot]

Pull Request Overview

This PR corrects the example model name used in the gh models run documentation to reference a valid model, and updates both the single-question and piped-command examples.

• Updated the single-question example to use a valid model name
• Updated the piped-context example to use a valid model name

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
github-models/use-github-models/integrating-ai-models-into-your-development-workflow.md	fpt ghec	fpt ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

Thanks for opening a PR! I'll get this triaged for review.

[InteligenceQ]

Yess

[Copilot]

Pull Request Overview

This PR updates the documentation for the gh models run command by replacing the incorrect model name "gpt-4.1" with the valid "openai/gpt-4.1".

• Updated example commands to utilize the correct model name across both single question and command output context scenarios.
• Ensures consistency with CLI help and available models.

[steveward]

Looks good, thanks @mgiovani!

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡