Merge pull request #9800 from cli/kw/update-docs-with-github-preview-terminology

Use new GitHub preview terms in `working-with-us.md`
This commit is contained in:
Kynan Ware 2024-10-22 12:40:14 -06:00 committed by GitHub
commit fd56fec110
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -25,13 +25,13 @@ Describe how your new command would be used. Include mock-up examples, including
We take this step seriously because we believe in keeping `gh`'s interface consistent and intuitive.
## Step 2: Beta
## Step 2: Public Preview
Once we've signed off on the proposed UX on the issue opened in step 1, develop your extension to at least beta quality. It's up to you if you actually want to go through a beta release phase with real users or not.
Once we've signed off on the proposed UX on the issue opened in step 1, develop your extension to at least public preview quality. It's up to you if you actually want to go through a public preview release phase with real users or not.
## Step 3: Merge or no merge
With a beta in hand it's time to decide whether or not to mainline your extension into the `trunk` of `gh`. Some questions to consider:
With a public preview in hand it's time to decide whether or not to mainline your extension into the `trunk` of `gh`. Some questions to consider:
- How complex is the support burden for your feature?