ci: watcher for automerge

[Borda]

As discussed in #428 (comment) adding a closure job would allow enabling automerge without need of updating branch protection checks when new Python version is added

[Borda]

now we could set these two as required checks:

cc: @hugovk

[hugovk]

👍

[hugovk]

👍

[Borda]

@dbieber any idea what is happening with the @CopyBara? as there are no details shared... 🤔

[dbieber]

Copybara is the tool we use to sync the google internal copy of the repo with the github copy. The error could be from them getting out of sync; I'll have to look into that. You can ignore that check in the mean time.

[Borda]

@dbieber how is it going? 🐿️

[Borda]

@dbieber can I help with anything else here? 🐰

[dbieber]

Thanks for checking back in, but unfortunately no, no updates on my end.

[Borda]

Gentle ping @dbieber 🐿️

[Borda]

@dbieber how are you doing, still with this project? 🐿️

[Borda]

hello @dbieber, happy New year! 🎆

[Borda]

@dbieber any chance to get some more details on what is happening with the copybara?

[dbieber]

@dbieber any chance to get some more details on what is happening with the copybara?

Hmm, I don't know offhand. Copybara is a tool we use to sync our internal and external codebases. I'll have to investigate.

[Borda]

I'll have to investigate.

lets try just restart it for now?

[dbieber]

You can safely ignore it.

[Borda]

You can safely ignore it.

the rest is green 🟢

[Borda]

@dbieber, so can we merge it? 🤔

[dbieber]

Hi Borda,

Thank you for the PR and your patience. I see the value of running the GitHub Actions on a pull_request. I do not see the value of the watcher job or auto-merge, however.

I understand that the watcher job would allow for auto-merge. Perhaps I am misunderstanding what auto-merge is, but it seems to me that I would like to review and approve PRs before they are merged, and hence I do not want to enable auto-merge on this project. Let me know if I'm misunderstanding auto-merge or missing something.

Cheers,
David

🐙

[Borda]

I understand that the watcher job would allow for auto-merge.

That is probably a misunderstanding; the watcher jobs just aggregated the result over the previously completed matrix of jobs... so the case is that in the GH setting you do not need to click all jobs one by one and if you change Python version it need to be also updated in the setting but you set as required only this one which is aggregated result of all

[Borda]

@dbieber, mind having a look and sharing your thoughts? 🦩
this will also be even more useful if we extend the testing matrix, ref #490

[Borda]

@dbieber friendly ping if you could have a look... 🐿️

[Borda]

@dbieber after the extended build matrix this gain its value as so safety you can set this watcher as required check and so all builds are required but without the need to name them one by one...

[Borda]

@dbieber after the extended build matrix this gain its value as so safety you can set this watcher as required check and so all builds are required but without the need to name them one by one...

mind check this one, and also add this rather to required checks?