sync-issue-templates

To sync issue templates from an organization's .github repository into the current repository, run the sync operation to copy org templates into the local repo's .github/ISSUE_TEMPLATE directory, preserving filenames and configuring blank issue behavior.

Yes, you can preserve or merge local issue templates when syncing from an organization .github repo. The process prompts before replacements or merges, allowing you to override local templates or keep existing configurations intact.

Centralized issue template management mirrors standardized templates from an organization's .github repo into individual repositories. You need it when managing multiple repositories to maintain consistency and reduce manual updates across your GitHub organization.

Yes, you need gh authentication to sync GitHub issue templates into your current repository. The current directory must be a GitHub-hosted repository, and gh authentication is required to access the organization's .github repository and write templates locally.

Synced organization issue templates are written to the .github/ISSUE_TEMPLATE directory in the current repository. The process preserves the original filenames from the organization's .github repository when copying the templates locally.

If you already have issue templates in your .github/ISSUE_TEMPLATE directory, the sync process will prompt you before replacements or merges. You can choose to preserve existing local templates or override them with the organization's centralized templates.