Add repo update and create-from-template#103
Merged
Merged
Conversation
lbrealdev
marked this pull request as ready for review
July 22, 2026 14:58
Contributor
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Drop the hand-maintained changelog and document releases via GitHub Release notes instead. Co-authored-by: akae <lbrealdev@users.noreply.github.com>
Map --new-name to the GitHub PATCH name field so repositories can be renamed without colliding with --name (current repo). Co-authored-by: akae <lbrealdev@users.noreply.github.com>
Allow marking or unmarking a repository as a GitHub template via PATCH is_template, distinct from create --template OWNER/REPO. Co-authored-by: akae <lbrealdev@users.noreply.github.com>
Include the field in the curated detail view so template status is visible without switching to JSON. Co-authored-by: akae <lbrealdev@users.noreply.github.com>
Apply I001 import sorting and RUF013 explicit Optional annotations so CI Lint passes under current ruff. Co-authored-by: akae <lbrealdev@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements two features tracked in #101 and #102:
repo update—PATCH /repos/{owner}/{repo}for description, homepage, visibility, default branch, archive state, rename via--new-name, and template status via--as-template/--no-templaterepo create --template OWNER/REPO—POST /repos/{template_owner}/{template_repo}/generate, with optional--include-all-branchesAlso removes
CHANGELOG.md; release notes live in GitHub Releases (see CONTRIBUTING.md).repo gettable output now includesis_templateso template status is visible without JSON.CLI examples
github-rest-cli repo update --name my-repo --description "Updated" --private github-rest-cli repo update --name my-repo --new-name renamed-repo github-rest-cli repo update --name my-repo --as-template github-rest-cli repo get --name my-repo github-rest-cli repo update --name my-repo --no-template github-rest-cli repo create --name my-app --template owner/template-repo --privateNotes
--templatecannot be combined with--empty--public/--privateonly (not--internal)--include-all-branchesrequires--template--nameis the current repository;--new-namerenames it--as-template/--no-templatemark or unmark a repo as a template (distinct from create--template)docs/cli.mdand READMETesting
uv run pytest— green includingis_templatetable field testsruff check/ruff formaton touched filesCloses #101
Closes #102