Justin Harringa

Note: we could clear out any PRs where DFIU no longer detects particular dependencies. That could potentially be its own command. ## Example We see a PR that is updating...

It could clear out any PRs where it's currently running for a particular dependency. ## Example We're updating `alpine` and see that we have another PR for `alpine`. We could...

Since I've kind of called out 2 different cases, it seems like when implementing the fix, we could decide to spawn new issues if it's too big to fit this...

Perhaps a way to handle this would be to create a branch with the full image name (e.g. `myregistry.something.com/namespace/image:tag@sha256:123456789abcdef...` - but would need to be [cleansed of '@', ':', and...

@afalko @npwolf perhaps Dependabot has already done the heavy lifting and there is no longer a need for `dockerfile-image-update`? https://github.com/dependabot/dependabot-core/tree/master/docker

Hi @ksrisurapaneni have you had a chance to take a look at https://docs.github.com/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api#abuse-rate-limits (referenced in the error)? Per previous concerns, we're expanding your search now so you may hit many...

That's awesome @RahulSurwade08! Welcome! We're open to pull request, questions, etc... https://github.com/salesforce/dockerfile-image-update#developer-guide is a good starting guide and https://opensource.guide/how-to-contribute/ is a good general guide. But feel free to hit us...

Do you happen to have examples/screenshots that could help here? I'm not sure I completely understand the problem statement. Are we saying that `all` does not post a contextual description?

It closes that old PR and opens a new one with the new message, correct? On Thu, Feb 3, 2022 at 12:17 PM Andrey Falko ***@***.***> wrote: > @justinharringa :...

`all` will close/open new right? 😉