Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Maintenance] Enable auto merge for patch level via Renovatebot bypass #409

Open
2 tasks done
devtobi opened this issue Feb 26, 2025 · 0 comments · May be fixed by #410
Open
2 tasks done

[Maintenance] Enable auto merge for patch level via Renovatebot bypass #409

devtobi opened this issue Feb 26, 2025 · 0 comments · May be fixed by #410
Labels
Priority: High The issue contains work with high priority. Type: Maintenance The issue contains maintenance work.
Milestone

Comments

@devtobi
Copy link
Member

devtobi commented Feb 26, 2025

Relevant component

No response

Problem description (optional)

No response

Desired solution

GitHub allows to use a bypass list to enable automerge and skip the requirement of CODEOWNERS file.
To make LCM easier, we should enable automerge for patch level for:

  • GitHub Actions
  • Docker image bumps
  • NPM
  • Maven

Pinning itself is not affected by this, as we will still use SHA values for the actions and Docker images.

See it-at-m/refarch-templates#823 (comment) for reference.

Considered alternatives (optional)

No response

Additional context (optional)

No response

No duplicate

  • I confirm that this issue is not a duplicate

Code of Conduct

  • I agree to follow this project's Code of Conduct
@devtobi devtobi added the Type: Maintenance The issue contains maintenance work. label Feb 26, 2025
@devtobi devtobi added the Priority: High The issue contains work with high priority. label Feb 26, 2025
@devtobi devtobi moved this from Open to Accepted in it@M RefArch Feb 26, 2025
@devtobi devtobi linked a pull request Feb 26, 2025 that will close this issue
6 tasks
@devtobi devtobi linked a pull request Feb 26, 2025 that will close this issue
6 tasks
@devtobi devtobi added this to the Release 1.0 milestone Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High The issue contains work with high priority. Type: Maintenance The issue contains maintenance work.
Projects
Status: Accepted
Development

Successfully merging a pull request may close this issue.

1 participant