bbs2gh: support setting custom property values after repository migration

Aperta
  • Qualcosa non va?
#1,628 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

@enyil ci sta già lavorando.

Dal 8/10/2026.

  • #1629 di @enyil — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
csharp, github
Ambito
cli

Direzione di ricerca

The work is in the bbs2gh migrate-repo command, where the proposed --custom-properties flag would be validated and then applied via PATCH /repos/{owner}/{repo}/properties/values after a successful migration. Linked PR #1629 already holds an implementation, so review that first rather than starting fresh. Done means the flag is validated up front, rejected with --queue-only and export-only modes, and reports property-update failures without suggesting a rerun.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Description

I'd like to add an optional --custom-properties flag to gh bbs2gh migrate-repo so users can apply custom property key/value pairs to the destination repository as part of the migration command, rather than running a separate update manually.

Example:

--custom-properties '{"environment":"production","teams":["platform","security"]}'

The proposed scope is bbs2gh only. This does not add the option to ado2gh, gei, or gl2gh.

Proposed behavior
  • Accept an inline JSON object with strings, arrays of strings (multi-select), and null (unset). Boolean properties use the strings "true" and "false".
  • Validate the JSON and incompatible options before starting migration work.
  • After the repository migration succeeds, apply the values using PATCH /repos/{owner}/{repo}/properties/values.
  • Require the properties to already be defined in the destination organization and the caller to have permission to edit their values.
  • Reject --queue-only and export-only operations, since no post-migration update can be guaranteed in those modes.
  • Report property-update failures explicitly while explaining that the migrated repository already exists and the migration should not be rerun.
  • Leave existing behavior unchanged when the flag is omitted. generate-script is not extended; users can add the flag to individual generated migrate-repo calls.
Important limitation and related issues

The currently exposed StartRepositoryMigrationInput GraphQL input does not have a custom-properties field, so this proposal applies values after a successful migration, not atomically at repository creation.

It therefore does not solve creation-time required-property policies or the scenarios in github/gh-gei#1558 and github/gh-gei#1563. Those need migration API support and are separate from this bbs2gh-only convenience feature.

An implementation is prepared on enyil/gh-gei:enyil-bbs2gh-custom-properties with regression coverage, README documentation, logging, and a release note. Opening this issue for maintainer feedback before submitting a PR, as requested by CONTRIBUTING.md.

Lingua principale
C#
Stelle
482
Fork
151
Merge medio
2g 18h
PR unite (30g)
5

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/gh-gei

Tutte le issue di github/gh-gei

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.