Rhys Koedijk

@eli-gc unfortunately I'm not sure if the timeout issue can be resolved in the scope of this project; My understanding is that this is an issue in [dependabot-core](https://github.com/dependabot/dependabot-core). See: -...

@epicstar thanks, I will investigate further and see what is different between the two environments

>1. The renaming of files towards using the lib makes a lot of sense. However, I'd prefer we did that in a separate PR before to be merged before this...

> If we can piggyback on the updated core logic then it simplifies the maintenance works. This is why I had started to keep the files up-to date but got...

@mburumaxwell this is _[mostly]_ feature complete now. I still need to fully test all config options, fix a few small bugs, and clean/optimise the code. However, I would be interested...

> I think this is generally okay. I cannot see anything of major concern yet in the updater. Issues may show up when we make it available for others to...

> Any tips on how to test this vnext update script? Unfortunately you can't test this new script in DevOps until the extension is updated (see: https://github.com/tinglesoftware/dependabot-azure-devops/pull/1216). However, you can...

@ahmetgul93 thanks for the report. could you please provide some more information on what you are seeing in your pull requests-- more specifically, a visualization of the branch history and...

@ahmetgul93 @caglanurcetinn I haven't got around to this yet, but hope to spend some time on it in the next few days; I haven't forgotten about it though.

I suspect this is caused by an issue introduced in https://github.com/tinglesoftware/dependabot-azure-devops/pull/1382. Once https://github.com/tinglesoftware/dependabot-azure-devops/pull/1478 is merged, it would be good to re-test this to see if it fixes this issue too.