This is a good start!

The tests make sense; it looks like you have them set up properly.

I was confused by the difference in nomenclature between allow and enable flags -- if they are both toggles that accept true or false, they should probably be named similarly.

Some other stuff:

• instead of -n, support -R as other commands do
• avoid printing a success message if nothing was changed

One final consideration at this point is around renaming. We've added gh repo rename, so it's not strictly necessary that this command can rename; but it might feel weird to not support it. For now it's okay to punt on renaming in this command and we can worry about it later.

Hi @g14a, instead of requesting changes, I've pushed some simplifications to the branch.

• The most important change is that the PATCH API request sent to update the repository will no longer contain all the parameters with their default values. Only explicitly edited fields are ever sent. This is accomplished by using pointer fields on the EditRepositoryInput struct and marking them as omitempty for JSON serialization. This avoids race conditions in repository updates, e.g. two different update operations that concurrently write to different fields on the same repository shouldn't reset each other's changes.
• To make defining flags with pointer receivers easier, I've added helper functions for this to the cmdutil package.
• A flag that wasn't passed at all will have its pointer value at nil. We can thus avoid excessive checks to cmd.Flags().Changed().
• I've dropped the check that raises an at least one merge option must be true error since it didn't make sense in the context of this command.
• I've also dropped the check for the validity of the --name flag. We let the server decide about the validity of values passed.
• For now, I've removed the flag for changing the privacy/visibility of the repository. We have to first decide on an API for explicitly changing the visibility of the repository, and I would suggest avoiding boolean flags like --private. How about: --visibility={public,private,internal}?
• For now, I've removed the flag to archive the repository since we have the gh repo archive command now.

Could you go over the changes to see if they make sense? Thank you! 🙇

This looks really clean with the new flag utility functions!