Require visibility confirmation in `gh repo edit` #9845

andyfeller · 2024-10-29T14:31:43Z

This commit modifies interactive and non-interactive behaviors around gh repo edit as well as providing greater information about the impact.

--help usage is expanded to highlight the most significant consequences of changing visibility
--help usage and interactive experience call out GitHub Docs content that act as source of truth about full consequences of various changes
gh repo edit interactive experience will require confirmation for any visibility change
gh repo edit interactive experience will output potential stars and watchers lose regardless of visibility transition
gh repo edit will require --visibility flag to include new --accept-visibility-change-consequences flag regardless of interactivity

Changes to user experience

--help explaining danger of visibility changes

./bin/gh repo edit --help
Edit repository settings.

To toggle a setting off, use the `--<flag>=false` syntax.

Changing repository visibility can have unexpected consequences including but not limited to:

- Losing stars and watchers, affecting repository ranking
- Detaching public forks from the network
- Disabling push rulesets
- Allowing access to GitHub Actions history and logs

When the `--visibility` flag is used, `--accept-visibility-change-consequences` flag is required.

For information on all the potential consequences, see <https://gh.io/setting-repository-visibility>

Initial disclaimer / warning in gh repo edit interactive mode

$ ~/Documents/workspace/cli/cli/bin/gh repo edit
? What do you want to edit? Visibility
! Danger zone: changing repository visibility can have unexpected consequences; consult https://gh.io/setting-repository-visibility before continuing.
? Visibility  [Use arrows to move, type to filter]
> public
  private
  internal

Confirmation prompt when 0 stars and 0 watchers

~/Documents/workspace/cli/cli/bin/gh repo edit
? What do you want to edit? Visibility
! Danger zone: changing repository visibility can have unexpected consequences; consult https://gh.io/setting-repository-visibility before continuing.
? Visibility private
? Do you want to change visibility to private? (y/N)

Confirmation prompt when 1 star

~/Documents/workspace/cli/cli/bin/gh repo edit
? What do you want to edit? Visibility
! Danger zone: changing repository visibility can have unexpected consequences; consult https://gh.io/setting-repository-visibility before continuing.
? Visibility private
! Changing the repository visibility to private will cause permanent loss of 1 star and 0 watchers.
? Do you want to change visibility to private? (y/N)

Confirmation prompt when 1 watcher

~/Documents/workspace/cli/cli/bin/gh repo edit
? What do you want to edit? Visibility
! Danger zone: changing repository visibility can have unexpected consequences; consult https://gh.io/setting-repository-visibility before continuing.
? Visibility private
! Changing the repository visibility to private will cause permanent loss of 0 stars and 1 watcher.
? Do you want to change visibility to private? (y/N)

Confirmation prompt when 1 star and 1 watcher

~/Documents/workspace/cli/cli/bin/gh repo edit
? What do you want to edit? Visibility
! Danger zone: changing repository visibility can have unexpected consequences; consult https://gh.io/setting-repository-visibility before continuing.
? Visibility private
! Changing the repository visibility to private will cause permanent loss of 1 star and 1 watcher.
? Do you want to change visibility to private? (y/N)

Confirmation prompt when 2+ stars and 2+ watchers

~/Documents/workspace/cli/cli/bin/gh repo edit
? What do you want to edit? Visibility
! Danger zone: changing repository visibility can have unexpected consequences; consult https://gh.io/setting-repository-visibility before continuing.
? Visibility private
! Changing the repository visibility to private will cause permanent loss of 2 stars and 2 watchers.
? Do you want to change visibility to private? (y/N)

This commit modifies interactive and non-interactive behaviors around `gh repo edit` as well as providing greater information about the impact. 1. `--help` usage is expanded to highlight the most significant consequences of changing visibility 1. `--help` usage and interactive experience call out GitHub Docs content that act as source of truth about full consequences of various changes 1. `gh repo edit` interactive experience will require confirmation for any visibility change 1. `gh repo edit` interactive experience will output potential stars and watchers lose regardless of visibility transition 1. `gh repo edit` will require `--visibility` flag to include new `--accept-visibility-change-consequences` flag regardless of interactivity

williammartin

How would you feel about applying the following patch to test the stargazer and watcher count message.

diff --git a/pkg/cmd/repo/edit/edit_test.go b/pkg/cmd/repo/edit/edit_test.go
index 728f19d45..42d6f346c 100644
--- a/pkg/cmd/repo/edit/edit_test.go
+++ b/pkg/cmd/repo/edit/edit_test.go
@@ -378,6 +378,9 @@ func Test_editRun_interactive(t *testing.T) {
 									"name": "main"
 								},
 								"stargazerCount": 10,
+								"watchers": {
+									"totalCount": 15
+								},
 								"isInOrganization": false,
 								"repositoryTopics": {
 									"nodes": [{
@@ -395,6 +398,7 @@ func Test_editRun_interactive(t *testing.T) {
 						assert.Equal(t, "private", payload["visibility"])
 					}))
 			},
+			wantsStderr: "Changing the repository visibility to private will cause permanent loss of 10 stars and 15 watchers",
 		},
 		{
 			name: "the rest",
@@ -631,7 +635,7 @@ func Test_editRun_interactive(t *testing.T) {
 
 	for _, tt := range tests {
 		t.Run(tt.name, func(t *testing.T) {
-			ios, _, _, _ := iostreams.Test()
+			ios, _, _, stderr := iostreams.Test()
 			ios.SetStdoutTTY(true)
 			ios.SetStdinTTY(true)
 			ios.SetStderrTTY(true)
@@ -653,10 +657,11 @@ func Test_editRun_interactive(t *testing.T) {
 			opts.IO = ios
 
 			err := editRun(context.Background(), opts)
+			require.Contains(t, stderr.String(), tt.wantsStderr)
 			if tt.wantsErr == "" {
 				require.NoError(t, err)
 			} else {
-				assert.EqualError(t, err, tt.wantsErr)
+				require.EqualError(t, err, tt.wantsErr)
 				return
 			}
 		})

williammartin · 2024-10-30T14:06:15Z

pkg/cmd/repo/edit/edit_test.go

 				pm.RegisterMultiSelect("What do you want to edit?", nil, editList,
 					func(_ string, _, opts []string) ([]int, error) {
-						return []int{0, 2, 3, 5, 6, 8, 9}, nil
+						return []int{0, 2, 3, 5, 6, 9}, nil


That's a yikes (not your fault)

I suspect the tight coupling of this code versus the code under test and the ordering of options is 🤢 which I agree isn't ideal.

williammartin

Thanks!

williammartin · 2024-10-30T18:30:34Z

pkg/cmd/repo/edit/edit.go

 			opts.Edits.EnableProjects = &a
 		case optionVisibility:
+			cs := opts.IO.ColorScheme()
+			fmt.Fprintf(opts.IO.ErrOut, "%s Danger zone: changing repository visibility can have unexpected consequences; consult https://gh.io/setting-repository-visibility before continuing.\n", cs.WarningIcon())


Just wondering why you chose ErrOut here. When we have TTYs I always feel a bit like everything should go to Out unless it's an actual error, but it seems very gray. I'm never really sure though.

In any case it's not a blocker and we can always change it later since this is interactive.

Just wondering why you chose ErrOut here. When we have TTYs I always feel a bit like everything should go to Out unless it's an actual error, but it seems very gray. I'm never really sure though.

I totally feel how big of a gray area this is! 💯 Let me capture my thoughts but here is cli/cli code use of ErrOut.

Suffice to say, I see informational output like this similar to CLIG guidance as something that really isn't machine readable content but messaging / informational:

Send output to stdout. The primary output for your command should go to stdout. Anything that is machine readable should also go to stdout—this is where piping sends things by default.

Send messaging to stderr. Log messages, errors, and so on should all be sent to stderr. This means that when commands are piped together, these messages are displayed to the user and not fed into the next command.

If someone was redirecting the output of this command somewhere, I wouldn't want this info to be swallowed up or treated differently if in non-TTY usage.

If someone was redirecting the output of this command somewhere, I wouldn't want this info to be swallowed up or treated differently if in non-TTY usage.

Right I get all that generally, but this is only TTY interactive usage. You can't get to these new messages otherwise, right?

This MR contains the following updates: | Package | Update | Change | |---|---|---| | [cli/cli](https://github.com/cli/cli) | minor | `v2.59.0` -> `v2.62.0` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>cli/cli (cli/cli)</summary> ### [`v2.62.0`](https://github.com/cli/cli/releases/tag/v2.62.0): GitHub CLI 2.62.0 [Compare Source](cli/cli@v2.61.0...v2.62.0) #### What's Changed - Update monotonic verification logic and testing by [@malancas](https://github.com/malancas) in cli/cli#9856 - Check extension for latest version when executed by [@andyfeller](https://github.com/andyfeller) in cli/cli#9866 - Shorten extension release checking from 3s to 1s by [@andyfeller](https://github.com/andyfeller) in cli/cli#9914 - Mention GitHub CLI team on discussion issues by [@andyfeller](https://github.com/andyfeller) in cli/cli#9920 **Full Changelog**: cli/cli@v2.61.0...v2.62.0 #### Security - A security vulnerability has been identified in GitHub CLI that could allow remote code execution (RCE) when users connect to a malicious Codespace SSH server and use the `gh codespace ssh` or `gh codespace logs` commands. For more information, see GHSA-p2h2-3vg9-4p87 #### GitHub CLI notifies users about latest extension upgrades Similar to the notification of latest `gh` releases, the `v2.62.0` version of GitHub CLI will notify users about latest extension upgrades when the extension is used: ```shell $ gh ado2gh ... A new release of ado2gh is available: 1.7.0 → 1.8.0 To upgrade, run: gh extension upgrade ado2gh --force https://github.com/github/gh-ado2gh ``` ##### Why does this matter? This removes a common pain point of extension authors as they have had to reverse engineer and implement a similar mechanism within their extensions directly. With this quality of life improvement, there are 2 big benefits: 1. Extension authors will hopefully see increased adoption of newer releases while having lower bar to maintaining their extensions. 2. GitHub CLI users will have greater awareness of new features, bug fixes, and security fixes to the extensions used. ##### What do you need to do? Extension authors should review their extensions and consider removing any custom logic previously implemented to notify users of new releases. ### [`v2.61.0`](https://github.com/cli/cli/releases/tag/v2.61.0): GitHub CLI 2.61.0 [Compare Source](cli/cli@v2.60.1...v2.61.0) #### Ensure users understand consequences before making repository visibility changes In `v2.61.0`, `gh repo edit` command has been enhanced to inform users about [consequences of changing visibility](https://gh.io/setting-repository-visibility) and ensure users are intentional before making irreversible changes: 1. Interactive `gh repo edit` visibility change requires confirmation when changing from `public`, `private`, or `internal` 2. Non-interactive `gh repo edit --visibility` change requires new `--accept-visibility-change-consequences` flag to confirm 3. New content to inform users of consequences - Incorporate [GitHub Docs content](https://gh.io/setting-repository-visibility) into help usage and interactive `gh repo edit` experience - Expanded help usage to call out most concerning consequences - Display repository star and watcher counts to understand impact before confirming #### What's Changed - Add acceptance test for `project` command by [@jtmcg](https://github.com/jtmcg) in cli/cli#9816 - Add comprehensive testscript for `gh ruleset` by [@andyfeller](https://github.com/andyfeller) in cli/cli#9815 - Add comprehensive testscript for gh ext commandset by [@andyfeller](https://github.com/andyfeller) in cli/cli#9810 - Require visibility confirmation in `gh repo edit` by [@andyfeller](https://github.com/andyfeller) in cli/cli#9845 - Clean up skipped online tests for `gh attestation verify` by [@malancas](https://github.com/malancas) in cli/cli#9838 - `gh attestation verify` should only verify provenance attestations by default by [@malancas](https://github.com/malancas) in cli/cli#9825 - Set `dnf5` commands as default by [@its-miroma](https://github.com/its-miroma) in cli/cli#9844 - Fix verbiage for deleting workflow runs by [@akx](https://github.com/akx) in cli/cli#9876 - Bump github.com/creack/pty from 1.1.23 to 1.1.24 by [@dependabot](https://github.com/dependabot) in cli/cli#9862 - `gh attestation verify` policy enforcement refactor by [@malancas](https://github.com/malancas) in cli/cli#9848 - Simplify Sigstore verification result handling in `gh attestation verify` by [@malancas](https://github.com/malancas) in cli/cli#9877 - Print empty array for `gh cache list` when `--json` is provided by [@williammartin](https://github.com/williammartin) in cli/cli#9883 - Bump actions/attest-build-provenance from 1.4.3 to 1.4.4 by [@dependabot](https://github.com/dependabot) in cli/cli#9884 - Create the automatic key when specified with -i by [@cmbrose](https://github.com/cmbrose) in cli/cli#9881 - fix: `gh pr create -w` ignore template flag by [@nilvng](https://github.com/nilvng) in cli/cli#9863 #### New Contributors - [@akx](https://github.com/akx) made their first contribution in cli/cli#9876 - [@nilvng](https://github.com/nilvng) made their first contribution in cli/cli#9863 **Full Changelog**: cli/cli@v2.60.1...v2.61.0 ### [`v2.60.1`](https://github.com/cli/cli/releases/tag/v2.60.1): GitHub CLI 2.60.1 [Compare Source](cli/cli@v2.60.0...v2.60.1) This is a small patch release to fix installing `gh` via `go install` which was broken with v2.60.0. #### What's Changed - Update testscript to use hard fork by [@williammartin](https://github.com/williammartin) in cli/cli#9821 **Full Changelog**: cli/cli@v2.60.0...v2.60.1 ### [`v2.60.0`](https://github.com/cli/cli/releases/tag/v2.60.0): GitHub CLI 2.60.0 [Compare Source](cli/cli@v2.59.0...v2.60.0) #### What's Changed - Add ArchivedAt field by [@tsukasaI](https://github.com/tsukasaI) in cli/cli#9790 - Include startedAt, completedAt in run steps data by [@andyfeller](https://github.com/andyfeller) in cli/cli#9774 - Adjust environment help for host and tokens by [@williammartin](https://github.com/williammartin) in cli/cli#9809 - Add handling of empty titles for Issues and MRs by [@jtmcg](https://github.com/jtmcg) in cli/cli#9701 - `LiveSigstoreVerifier.Verify` should error if no attestations are present by [@phillmv](https://github.com/phillmv) in cli/cli#9742 - `gh at verify` retries fetching attestations if it receives a 5xx by [@phillmv](https://github.com/phillmv) in cli/cli#9797 - Prevent local extension installations with invalid names and conflicts with core commands and other extensions by [@BagToad](https://github.com/BagToad) in cli/cli#9794 - Rewrite a sentence in CONTRIBUTING.md by [@muzimuzhi](https://github.com/muzimuzhi) in cli/cli#9772 - Use new GitHub preview terms in `working-with-us.md` by [@BagToad](https://github.com/BagToad) in cli/cli#9800 - Use new GitHub previews terminology in attestation commands' help docs by [@BagToad](https://github.com/BagToad) in cli/cli#9799 - Clarify in README that `gh` is supported on GitHub Enterprise Cloud by [@BagToad](https://github.com/BagToad) in cli/cli#9805 - build(deps): bump github.com/gabriel-vasile/mimetype from 1.4.5 to 1.4.6 by [@dependabot](https://github.com/dependabot) in cli/cli#9752 ##### Acceptance Test Changes - Add acceptance tests for `workflow`, `run`, and `cache` commands by [@BagToad](https://github.com/BagToad) in cli/cli#9766 - Add basic `api` acceptance tests by [@BagToad](https://github.com/BagToad) in cli/cli#9770 - Add acceptance tests for `release` commands by [@BagToad](https://github.com/BagToad) in cli/cli#9771 - Add acceptance tests for `org` and `ssh-key` commands by [@BagToad](https://github.com/BagToad) in cli/cli#9812 - Add acceptance tests for `gh auth` commands by [@jtmcg](https://github.com/jtmcg) in cli/cli#9787 - Add acceptance tests for `repo` commands by [@jtmcg](https://github.com/jtmcg) in cli/cli#9783 - Add acceptance tests for `search` command by [@BagToad](https://github.com/BagToad) in cli/cli#9786 - Add acceptance tests for `variable` commands by [@andyfeller](https://github.com/andyfeller) in cli/cli#978 - Add testscripts for gpg-key and label commands by [@williammartin](https://github.com/williammartin) in cli/cli#9811 - Use forked testscript for token redaction by [@williammartin](https://github.com/williammartin) in cli/cli#9804 - Add acceptance tests for `secret` commands by [@andyfeller](https://github.com/andyfeller) in cli/cli#9782 - Note token redaction in Acceptance test README by [@williammartin](https://github.com/williammartin) in cli/cli#9813 #### New Contributors - [@tsukasaI](https://github.com/tsukasaI) made their first contribution in cli/cli#9790 **Full Changelog**: cli/cli@v2.59.0...v2.60.0 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

andyfeller requested a review from a team as a code owner October 29, 2024 14:31

andyfeller requested a review from jtmcg October 29, 2024 14:31

cliAutomation added the external pull request originating outside of the CLI core team label Oct 29, 2024

williammartin reviewed Oct 30, 2024

View reviewed changes

Assert stderr for gh repo edit visibility tests

3f5fc85

andyfeller requested a review from williammartin October 30, 2024 17:38

williammartin approved these changes Oct 30, 2024

View reviewed changes

andyfeller merged commit 3b4301f into trunk Oct 30, 2024

andyfeller deleted the andyfeller/9807-repo-edit-visibility-confirmation branch October 30, 2024 19:20

BagToad mentioned this pull request Nov 30, 2024

Document the dangers of changing repo visibility in the CLI #9801

Closed

1 task

jtmcg mentioned this pull request Feb 4, 2025

Add the ability to delete the "last" comment, similar to --edit-last #10366

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Require visibility confirmation in `gh repo edit` #9845

Require visibility confirmation in `gh repo edit` #9845

Uh oh!

andyfeller commented Oct 29, 2024 •

edited

Loading

Uh oh!

williammartin left a comment

Uh oh!

williammartin Oct 30, 2024

Uh oh!

andyfeller Oct 30, 2024

Uh oh!

williammartin left a comment

Uh oh!

williammartin Oct 30, 2024

Uh oh!

andyfeller Oct 30, 2024 •

edited

Loading

Uh oh!

williammartin Oct 31, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Require visibility confirmation in gh repo edit #9845

Require visibility confirmation in gh repo edit #9845

Uh oh!

Conversation

andyfeller commented Oct 29, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes to user experience

Uh oh!

williammartin left a comment

Choose a reason for hiding this comment

Uh oh!

williammartin Oct 30, 2024

Choose a reason for hiding this comment

Uh oh!

andyfeller Oct 30, 2024

Choose a reason for hiding this comment

Uh oh!

williammartin left a comment

Choose a reason for hiding this comment

Uh oh!

williammartin Oct 30, 2024

Choose a reason for hiding this comment

Uh oh!

andyfeller Oct 30, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

williammartin Oct 31, 2024

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Require visibility confirmation in `gh repo edit` #9845

Require visibility confirmation in `gh repo edit` #9845

andyfeller commented Oct 29, 2024 •

edited

Loading

andyfeller Oct 30, 2024 •

edited

Loading