containers / containers/BuildSourceImage
TODOs
- Lingua principale
- Shell
- Stelle
- 32
- Fork
- 13
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
```bash
$ git grep -nw TODO BuildSourceImage.sh
BuildSourceImage.sh:6:# TODO maybe a flag for this?
BuildSourceImage.sh:45: # TODO: maybe this could be individual checks so it can report
BuildSourceImage.sh:267: ## TODO: check for authfile, creds, and whether it's an insecure registry
BuildSourceImage.sh:308: ## TODO: check for authfile, creds, and whether it's an insecure registry
BuildSourceImage.sh:387: # TODO this will need to be refactored when we start seeing +zstd layers.
BuildSourceImage.sh:451: ## TODO: check for authfile, creds, and whether it's an insecure registry
BuildSourceImage.sh:618: # TODO account for "artifact_path" being a directory?
BuildSourceImage.sh:625: # TODO this symlink need to be relative path, not to `/blobs/...`
BuildSourceImage.sh:629: # TODO this symlink need to be relative path, not to `/blobs/...`
BuildSourceImage.sh:685: # TODO account for "artifact_path" being a directory?
BuildSourceImage.sh:692: # TODO this symlink need to be relative path, not to `/blobs/...`
BuildSourceImage.sh:696: # TODO this symlink need to be relative path, not to `/blobs/...`
BuildSourceImage.sh:873: # TODO one day, check and confirm with %{sourcepkgid}
BuildSourceImage.sh:1219: # TODO probably just _error here to exit
BuildSourceImage.sh:1227: # TODO maybe look to a directory like /usr/libexec/BuildSourceImage/drivers/ for drop-ins to run
```
(as of efd2679729edadaacd2e8c26f247b22912910012)
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Start by reviewing BuildSourceImage.sh at the TODO locations listed in the issue and run the provided git grep command at the referenced commit. Determine which TODOs are actionable and define acceptance criteria for each; the issue does not currently specify what done looks like or identify tests to run.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- bash
- Ambito
- tooling
- Tipo di issue
- Refactoring
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 20/100