issue-fields-migration
Bulk-migrate metadata to GitHub issue fields from two sources: repo labels (e.g
by githubFree
Description
issue-fields-migration is an agent skill from the github/awesome-copilot collection that bulk-migrates metadata into GitHub issue fields. Issue fields are organization-level typed metadata, such as single select, text, number and date, which replace label-based workarounds with structured, searchable fields that work across repositories. Every organization has Priority, Effort, Start date and Target date set up, with room for up to twenty-five custom fields. The skill moves existing metadata from two sources. The first is repository labels, such as p0, p1 or priority/high, which are converted into values of a structured field such as Priority; several labels can be migrated at once, and they can optionally be removed afterward. The second is the field values in a GitHub Project V2, which are copied into the equivalent organization-level issue fields for single select, text, number, date and iteration fields. It is useful when an organization has added issue fields that overlap with project fields and wants to move the data before deleting the old fields, and when a team wants to clean up labels after adopting issue fields. Because the migration writes to many issues and can remove labels, the skill's steps should be run first on a test repository or a small set, and the labels to remove should be checked before the change. The skill is installed with the skills CLI from the github/awesome-copilot repository. Its skills.sh page showed about 1.9K installs, with Gen Agent Trust Hub and Socket passing and Snyk showing a warning at the time of the scan.…
Highlights
- Migrates labels to structured issue field values
- Copies Project V2 field values to issue fields
- Optional removal of migrated labels
- Supports single select, text, number, date and iteration fields
- Installs with the skills CLI
Ratings & Reviews
No ratings yet
Be the first to rate issue-fields-migration.
People also visit
az-cost-optimize
Analyze Azure resources and IaC files to identify cost optimizations
create-github-issues-for-unmet-specification-requirements
Automatically create GitHub issues
gen-specs-as-issues
Systematic workflow for identifying missing features, prioritizing them
issue-fields-migration FAQ
What are GitHub issue fields?
Organization-level typed metadata such as single select, text, number and date, which replace label-based workarounds.
What two sources can it migrate from?
Repository labels such as p0 or priority/high, and the field values in a GitHub Project V2.
Can it remove labels after migrating?
Yes, optionally. Check the labels to remove before running it.
Should I test first?
Yes. The migration writes to many issues, so run it on a test repository or a small set first.
How do I install it?
Run npx skills add https://github.com/github/awesome-copilot --skill issue-fields-migration.
What security audits does it have?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Warn. A Warn or Fail is worth reading before you install.
What are the best issue-fields-migration alternatives?
Popular alternatives to issue-fields-migration include az-cost-optimize, breakdown-plan and create-github-issues-for-unmet-specification-requirements. See all issue-fields-migration alternatives