Add auto merge for pre commit and dependabot in a CI job

[uittenbroekrobbert]

Description

Add a CI job to auto merge updates done by dependabot and pre-commit. Merges for dependabot are only done if minor or patch. For pre-commit it updates everything, as we don't have that level of control.

Resolves #

https://github.com/orgs/MinBZK/projects/7?pane=issue&itemId=65105178

Checklist

Please check all the boxes that apply to this pull request using "x":

Most changes are GitHub actions and those can not be tested locally. Pre-commit has been tested locally.

• I have tested the changes locally and verified that they work as expected.
• I have followed the project's coding conventions and style guidelines.
• I have rebased my branch onto the latest commit of the main branch.
• I have squashed or reorganized my commits into logical units.
• I have read, understood and agree to the Developer Certificate of Origin, which this project utilizes.

[github-actions]

Welcome to our community 🤗 and thank you for your first contribution.

As a first time contributor please make sure to review our contribution guidelines ❤️

[berrydenhartog]

Could you also add a CI workflow that build/lint the project?

[uittenbroekrobbert]

Could you also add a CI workflow that build/lint the project?

@berrydenhartog

I assume this would be steps to perform before approve / merge, so it becomes something like:
steps:

• checkout project
• lint project (abort if failed)
• build project (abort if failed)
• (optional) test project (abort if failed)
• approve
• merge

Is it worth looking into reusable workflows (have you done that before?), it seems like a good way to avoid code duplication but is some more work to set up:
https://docs.github.com/en/actions/using-workflows/reusing-workflows

[berrydenhartog]

Could you also add a CI workflow that build/lint the project?

@berrydenhartog

I assume this would be steps to perform before approve / merge, so it becomes something like: steps:

* checkout project

* lint project (abort if failed)

* build project (abort if failed)

* (optional) test project (abort if failed)

* approve

* merge

Is it worth looking into reusable workflows (have you done that before?), it seems like a good way to avoid code duplication but is some more work to set up: https://docs.github.com/en/actions/using-workflows/reusing-workflows

Indeed. but the approve and merge is done by your current action.
in another action you could implement a very simple ci job that builds the package and runs a linter:

example:

<install deps>
poetry build
poetry run ruff 
poetry run pyright

[berrydenhartog]

Reusable workflows could be usefull, but often i do not see them used because everyone wants control over there pipeline.

[berrydenhartog]

LGTM

[berrydenhartog]

Lgtm