l request as ready for review.

			Without an argument, the pull request that belongs to the current branch
			is marked as ready.

			If supported by your plan, convert to draft with %[1]s--undo%[1]s
		
			# Mark the github org's project "1" as a template
			$ gh project mark-template 1 --owner "github"

			# Unmark the github org's project "1" as a template
			$ gh project mark-template 1 --owner "github" --undo
		
			# Publish a release that was previously a draft
			$ gh release edit v1.0 --draft=false

			# Update the release notes from the content of a file
			$ gh release edit v1.0 --notes-file /path/to/release_notes.md
		
			View a specific repository license by license key or SPDX ID.

			Run %[1]sgh repo license list%[1]s to see available commonly used licenses. For even more licenses, visit <https://choosealicense.com/appendix>.
		accesskey,autocapitalize,autofocus,class,contenteditable,dir,draggable,enterkeyhint,hidden,id,inert,inputmode,is,itemid,itemprop,itemref,itemscope,itemtype,lang,part,role,slot,spellcheck,style,tabindex,title,translate
			# Watch a run until it's done
			$ gh run watch

			# Watch a run in compact mode
			$ gh run watch --compact

			# Run some other command when the run is finished
			$ gh run watch && notify-send 'run is done!'
		
			# Select what host and account to switch to via a prompt
			$ gh auth switch

			# Switch the active account on a specific host to a specific user
			$ gh auth switch --hostname enterprise.internal --user monalisa
		
			View an available repository %[1]s.gitignore%[1]s template.

			%[1]s<template>%[1]s is a case-sensitive %[1]s.gitignore%[1]s template name.

			For a list of available templates, run %[1]sgh repo gitignore list%[1]s.
		
			Download assets from a GitHub release.

			Without an explicit tag name argument, assets are downloaded from the
			latest release in the project. In this case, %[1]s--pattern%[1]s or %[1]s--archive%[1]s
			is required.
		
			Display labels in a GitHub repository.

			When using the %[1]s--search%[1]s flag results are sorted by best match of the query.
			This behavior cannot be configured with the %[1]s--order%[1]s or %[1]s--sort%[1]s flags.