Summary
When trying to yank a buildpack from the registry with pack buildpack yank, the command works to create a new PR, but it does not submit a valid issue body.
The body generated does not have the triple back ticks, nor does it have yank = true.
The code has this template hard coded and it needs to be updated:
Reproduction
Steps
Run pack buildpack yank foo-ns/foo-bp@1.2.3.
It generates:
id = "foo-ns/foo-bp"
version = "1.2.3"
It should generate...
```
id = "foo-ns/foo-bp"
version = "1.2.3"
yank = true
```
Example PR where this works: buildpacks/registry-index#13045
There is also a template in the registry-index project. I submitted a PR to update that. It would be nice if the go cli command just used this template instead of hard coding the title/body. Not sure if that is feasible.
Summary
When trying to yank a buildpack from the registry with
pack buildpack yank, the command works to create a new PR, but it does not submit a valid issue body.The body generated does not have the triple back ticks, nor does it have
yank = true.The code has this template hard coded and it needs to be updated:
Reproduction
Steps
Run
pack buildpack yank foo-ns/foo-bp@1.2.3.It generates:
It should generate...
Example PR where this works: buildpacks/registry-index#13045
There is also a template in the registry-index project. I submitted a PR to update that. It would be nice if the go cli command just used this template instead of hard coding the title/body. Not sure if that is feasible.