As noted the image for the Silveblue for developers magazine article was not committed, this corrects the error.
Not sure why, but this PR can't be merged. Can you please rebase and then update the PR?
I sure can
On Fri, 2020-06-19 at 15:29 +0000, Ben Cotton wrote:
bcotton commented on the pull-request: Forgot to push this from the SBfor Dev article that you are following: Not sure why, but this PR can't be merged. Can you please rebase and then update the PR? To reply, visit the link below or just reply to this email https://pagure.io/fedoramagazine-images/pull-request/112
bcotton commented on the pull-request: Forgot to push this from the SBfor Dev article that you are following: Not sure why, but this PR can't be merged. Can you please rebase and then update the PR?
Forgot to push this from the SBfor Dev article
To reply, visit the link below or just reply to this email https://pagure.io/fedoramagazine-images/pull-request/112
I had a similar problem I created with the SB documentation repo, recovering was convoluted if I remember correctly. I did the rebase and still can't seem to merge this due to conflicts. Should I just cancel the PR and do a new one?
Sure. In the future for new images,it's probably fine just to push directly to the repo (you should have access now)
Pull-Request has been closed by jakfrost
Hello Ben,
I re-cloned the images repo and deleted my local fork as to avoid confusing myself ... and git. Now I just have to find out how to get rid of my fork on Pagure
Stephen
On Fri, 2020-06-19 at 16:27 +0000, Ben Cotton wrote:
bcotton commented on the pull-request: Forgot to push this from the SBfor Dev article that you are following: Sure. In the future for new images,it's probably fine just to push directly to the repo (you should have access now) To reply, visit the link below or just reply to this email https://pagure.io/fedoramagazine-images/pull-request/112
bcotton commented on the pull-request: Forgot to push this from the SBfor Dev article that you are following: Sure. In the future for new images,it's probably fine just to push directly to the repo (you should have access now)
As noted the image for the Silveblue for developers magazine article was not committed, this corrects the error.