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

Dependabot Configuration #249

Closed
ja-fra opened this issue Apr 24, 2024 · 2 comments · Fixed by #250 or #257
Closed

Dependabot Configuration #249

ja-fra opened this issue Apr 24, 2024 · 2 comments · Fixed by #250 or #257
Assignees
Labels
dependencies Pull requests that update a dependency file enhancement New feature or request

Comments

@ja-fra
Copy link
Member

ja-fra commented Apr 24, 2024

Update the Dependabot configuration:

  • Dependency-Updates should target the develop-branch
  • Group Updates for: docker, official actions, common maven plugins
  • Simple Dependabot automation
@ja-fra ja-fra added enhancement New feature or request dependencies Pull requests that update a dependency file labels Apr 24, 2024
@ja-fra ja-fra self-assigned this Apr 24, 2024
ja-fra added a commit that referenced this issue Apr 24, 2024
@ja-fra ja-fra linked a pull request Apr 24, 2024 that will close this issue
ja-fra added a commit that referenced this issue Apr 24, 2024
@alireza-dhp
Copy link
Member

@ja-fra
Should the target-branch: 'develop' change to the target-branch: 'main' when it is merged into the main branch?

@ja-fra
Copy link
Member Author

ja-fra commented Apr 26, 2024

Should the target-branch: 'develop' change to the target-branch: 'main' when it is merged into the main branch?

No. We agreed that the dependency-updates should target the develop-branch, but to have dependabot pick this up it needs to be pushed to the default branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file enhancement New feature or request
2 participants