Flow.Launcher
Flow.Launcher copied to clipboard
Flow-Launcher
Add github dependency bot
Upping the versions will require testing, would it not be better to test while you are choosing to upgrade the version?
This will create a lot of noise in the pr section
Upping the versions will require testing, would it not be better to test while you are choosing to upgrade the version?
This will create a lot of noise in the pr section
We can make that check weekly/monthly, which means it will only create a version update pr once a week/month. In most situation, we don't update version because we are lazy to update hhh🤣 (or not notice there's an update).
Isn't this going to run through and create a pr for every version upgrade? This is going to create a fair bit prs.
Again you have to test to do the upgrade, which I would prefer effort put into enhancements instead and upgrade the required packages if needed
Isn't this going to run through and create a pr for every version upgrade? This is going to create a fair bit prs.
I don't think so. It shall create one pr once a week for all update if it has detected an update.
Again you have to test to do the upgrade, which I would prefer effort put into enhancements instead and upgrade the required packages if needed
Unless there's a breaking change (like squirrel), I don't think updating the a dependency will require a lot of testing.
We have a lot of old packages, it's going to upgrade a lot of them.
Can you check how many updates it will create for please
It will behave like this. Each update with an pull request, and it will list the release note and commit difference for each update.
https://github.com/taooceros/Flow.Launcher/pull/10
only 5 packages need updating?
No, it is because we can limit the count of pr created one time (which is 5)
Would it be better before applying the bot to make an individual branch, upgrade all the non-breaking upgrades on this branch, test them out and merge into dev first?
Would it be better before applying the bot to make an individual branch, upgrade all the non-breaking upgrades on this branch, test them out and merge into dev first?
Sounds reasonable
We have a lot of prs in the pipeline atm, will this change add a lot more? If so can we bump all NuGet packages on a seperate branch, test everything ok and merge in before merging this one so we start with a good baseline.
You can limit the maximum PR's dependabot is able to create with: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#open-pull-requests-limit
You can limit the maximum PR's dependabot is able to create with: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#open-pull-requests-limit
the default is 5, which I think is quite reasonable
Seems reasonable to me. Our tests will still run on each PR so in theory we get updated packages for free.