Try to improve autoupdate

[derberg]

Reason/Context

The autoupdate workflow doesn't work with forks.

It can update only branches that are in the upstream.

Description

When the branch from the fork is out of sync with master, in the UI maintainers see a button that they can click to update the branch with master.

We should allow anyone to be able to trigger such an update.

If there is a button, there needs to be API behind it, REST or GraphQL. There needs to be a research on how to trigger such branch update in form with an API. Then we need to update autoupdate workflow

[Shurtu-gal]

@derberg Can I work upon this?

[derberg]

sure, go ahead

[Shurtu-gal]

• Should the updation of branch be automatic or manual?
• Also anyone includes everyone or some specific group of people?
• What should be done in case of merge conflicts?

cc - @derberg

[derberg]

• it should be manual, like use should pass come comment into PR, like /update
• anyone
• I think there is already a workflow that detects that where merge conflict is in place, and someone attempts to merge, bot drops a message about it. So basically extend this workflow to be triggered/used in case somebody do /update but it fails because of merge conflict

[Shurtu-gal]

@derberg, can you please tell me the secrets stored in the repo so that I can introduce them into the code?

Also, the updation of forks requires a maintainer level of access, if I am not wrong. 😓

[derberg]

sorry, was out on holidays

yeah, I cannot give you secrets, this is why these are secrets 😛

Also, the updation of forks requires a maintainer level of access, if I am not wrong

yes, and our bots are maintainers in all repos, so that will work

[derberg]

you probably need to setup alternative test account to test it. I do it on my own too, have 2 GH accounts, one that you see here and the other purely for testing

[Shurtu-gal]

Got it 😄

[derberg]

/help

[asyncapi-bot]

Hello, @derberg! 👋🏼

I'm 🧞🧞🧞 Genie 🧞🧞🧞 from the magic lamp. Looks like somebody needs a hand!

At the moment the following comments are supported in issues:

• /good-first-issue {js | ts | java | go | docs | design | ci-cd} or /gfi {js | ts | java | go | docs | design | ci-cd} - label an issue as a good first issue.
  example: /gfi js or /good-first-issue ci-cd