in theory, this flow might be evolved

1) currently there's automation which closes every PR. automation is hidden
somewhere and only few people can modify it

2) the same automation might be implemented using Github Actions (closing
PR, sending email to list, etc), and there's a space for customization,
certain PRs (from dependabot) might be handled in different way

I think, dependabot adds small improvement, it is automated monitoring.
but I agree that will be noisy and not very useful.

вт, 24 мая 2022 г. в 12:27, Tim Düsterhus <t...@bastelstu.be>:

> Hi
>
> On 5/24/22 03:23, PR Bot wrote:
> > Dear list!
> >
> > Author: naveen <172697+naveensriniva...@users.noreply.github.com>
> > Number of patches: 1
> >
> > This is an automated relay of the Github pull request:
> >     chore: Included githubactions in the dependabot config
> >
> > Patch title(s):
> >     chore: Included githubactions in the dependabot config
> >
>
> I disagree with this patch. This does not bring a real benefit for us
> and only increases the noise by more (automated) pull requests.
>
> What the PR does is basically setting up automated pull requests for
> patches like these:
>
>
> https://github.com/haproxy/haproxy/commit/5f4ddb54b05ae0355b1f64c22263a6bc381410df
>
> I keep track of that and send patches as appropriate.
>
> Best regards
> Tim Düsterhus
>
>

Reply via email to