[Backport maintenance/3.3.x] Use custom Github App to authenticate backport job

[pylint-backport-bot]

Backport 6be8676 from #10394.

[cdce8p]

What do you guys think @Pierre-Sassoulas @DanielNoord ?

The only small thing left would be to change the commit author in the tibdex/backport action. It's still set to github-actions[bot]@users.noreply.github.com. At least for squash merge commits that shouldn't really matter though with

This commit will be authored by 212256041+pylint-backport-bot[bot]@users.noreply.github.com.

https://github.com/tibdex/backport/blob/main/src/backport.ts#L260-L266

[DanielNoord]

LGTM!

[Pierre-Sassoulas]

LGTM, that would be for style point, we already have 150+ commits from github actions bot and the co-author is properly set anyway. (Beside we do not control the tidbex/backport so it could take some time)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.84%. Comparing base (7038ef4) to head (526eb86).
Report is 1 commits behind head on maintenance/3.3.x.

Additional details and impacted files

@@                Coverage Diff                 @@
##           maintenance/3.3.x   #10396   +/-   ##
==================================================
  Coverage              95.84%   95.84%           
==================================================
  Files                    174      174           
  Lines                  18999    18999           
==================================================
  Hits                   18210    18210           
  Misses                   789      789           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[cdce8p]

LGTM, that would be for style point, we already have 150+ commits from github actions bot and the co-author is properly set anyway.

The author for the squash-merge commit will be fine as well. It's just 526eb86 that's not entirely correct.

(Beside we do not control the tidbex/backport so it could take some time)

True. No commits in over two years. We would probably have to fork it into the pylint-dev org but that could be done. Making the author configurable should be fairly strait forward.

[Pierre-Sassoulas]

We would probably have to fork it into the pylint-dev org but that could be done.

There's also some advantages of not having to review new versions or worry about supply chain attacks.

If you want to do it and it seems you want to do it, let's do it 😉

[cdce8p]

If you want to do it and it seems you want to do it, let's do it 😉

I'll probably finish #10382 first but after that 😄