Use custom backport action

[cdce8p]

Description

Followup to #10396

I finally got around to forking and updating the backport action. I can be found here
https://github.com/pylint-dev/backport
tibdex/backport@main...pylint-dev:backport:main

The plan is to due only the bare minimum of maintenance there. So far I've

• Updated node to v24 and the dependencies
• Fixed some workflows
• Added user_name and user_email options

I've configured the vars in the pylint-dev org selected for the pylint and astroid repos.

Open question

Should we rename the pylint-backport-bot[bot] to just pylint-backport[bot]? When I did set it up, I didn't know that Github would add [bot] automatically. It's probably just a style thing. At most some commits in the maintenance branch won't be probably attributed to the bot anymore.

I lean slightly towards doing it.

--
Will tag this one for the backport, just so we can see if everything worked out fine.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.84%. Comparing base (2d60c59) to head (6c6d2a4).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@ ## main #10536 +/- ## ========================================== - Coverage 95.84% 95.84% -0.01%  ========================================== Files 177 177 Lines 19282 19278 -4 ========================================== - Hits 18481 18477 -4  Misses 801 801 

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[github-actions]

🤖 According to the primer, this change has no effect on the checked open source code. 🤖🎉

This comment was generated for commit 6c6d2a4

[Pierre-Sassoulas]

Great ! Let's not move too much from the main branch in case we want to rebase on it or go back to it maybe ?

[cdce8p]

Let's not move too much from the main branch in case we want to rebase on it or go back to it maybe ?

I agree. My main focus here was to a) bring it in a maintainable state / fix all security warnings and b) implement the user name and email inputs. I don't plan to do any more changes at the moment. https://github.com/pylint-dev/backport/security/dependabot?q=is%3Aclosed

Tbh though I don't know if the upstream repo is even still maintained anymore. There hasn't been any activity for over two years. https://github.com/tibdex/backport

Should we rename the pylint-backport-bot[bot] to just pylint-backport[bot]?

Just did that, looks like it worked out fine. All past commits are still attributed correctly.