The proxy will start requiring one.

See merge request !40

This was removed, as the assumption was that the proxy server would hold
the token and we do not need to provide it ourselves.

This means that the proxy would have to be protected to allow only
connections from proxy-qa-bot.

It's better to provide the token and use the proxy as an escalation
mechanism. This works better as it allow us to deploy the proxy
somewhere else.

The token is used to authenticate incoming webhooks, so rename the
configuration to avoid confusion.

It is utterly broken (just closes any MR), and disabling it apparently
does not suffice.

This was done before in a separate [project][0], but that means each release
of this project requires a bump in the other project.

We can simplify this, especially now that we can use the gitlab
container registry.

[0]:https://gitlab.alpinelinux.org/alpine/infra/docker/aports-qa-bot

See merge request !39

This was done before in a separate project[0], but that means each release
of this project requires a bump in the other project.

We can simplify this, especially now that we can use the gitlab
container registry.

[0]:https://gitlab.alpinelinux.org/alpine/infra/docker/aports-qa-bot

the URL of the previous comment is now obselete (doesn't exist in 14.x
and 15-pre versions of GitLab), so we are updating it and also
conforming to the new advice that is present.

See merge request !37

Leo authored Apr 24, 2022 and Kevin Daudt committed Dec 25, 2022

the URL of the previous comment is now obselete (doesn't exist in 14.x
and 15-pre versions of GitLab), so we are updating it and also
conforming to the new advice that is present.

This new service is supposed to comment on new opened MRs which
modify an APKBUILD maintained by a team

Relates alpine/tsc#46

This is necessary to reuse the function in other services. Additionally,
add and return a Maintainer struct, which allows to extend the information
provided or stored in the maintainer part.

Also, one duplicated test has been removed.

there is no returning HTTP status code anywhere after the comment since
it was moved up in accordance with GitLab best practices

there are other operations that are also done like adding v<VERSION> for
backports to stable branches and in the future adding `tag:security`
label.

As such we should not return early if we fail to get changes, but still
we should log an ERROR instead of an WARN because failing here causes a
non-total but significant lost of expected functionality.

as required by newer versions of go-gitlab

in a future commit we will upgrade all the dependencies

labels received from a MergeRequest EventType are now a pointer which
can be nul if there are labels, this makes sense and was added in this
commit

https://github.com/xanzy/go-gitlab/commit/6fbe1d965d6be4e1109db089e9a60ae49e909e0c#diff-7771f19b44db1a454b9aec3b0243830c71911891658ea3d9831a498d9d33a8df

so we need to adapt our ContainsLabel helper function to make good use
of it

turns out it is not a light object, so use a pointer to it