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.

Sign up for GitHub

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

Jump to bottom

Maintenance: adopt Dependabot multi-directory config #2454

Closed
1 of 2 tasks
dreamorosi opened this issue Apr 30, 2024 · 2 comments · Fixed by #2532
Closed
1 of 2 tasks

Maintenance: adopt Dependabot multi-directory config #2454

dreamorosi opened this issue Apr 30, 2024 · 2 comments · Fixed by #2532
Assignees
@daschaa
Labels
automation This item relates to automation confirmed The scope is clear, ready for implementation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)

Comments

@dreamorosi
Copy link
Contributor

Summary

GitHub just announced a public beta for multi-directory configurations for Dependabot.

Today our Dependabot config has multiple entries for the same package manager, for example here and here.

This new setting allows us to specify multiple directories under the same config group.

Why is this needed?

So that the Dependabot config is simplified.

Which area does this relate to?

Automation

Solution

No response

Acknowledgment

Future readers

Please react with 👍 and your use case to help us understand customer demand.
@dreamorosi dreamorosi added automation This item relates to automation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) confirmed The scope is clear, ready for implementation labels Apr 30, 2024
@daschaa
Copy link
Contributor

daschaa commented May 16, 2024

I would like to take this issue :)

@daschaa daschaa mentioned this issue May 16, 2024
Merged
@github-actions GitHub Actions
Copy link
Contributor

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@daschaa daschaa

Labels
automation This item relates to automation confirmed The scope is clear, ready for implementation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
Powertools for AWS Lambda (TypeScript)
Status: Coming soon
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(ci): Adopt multi directory config for dependabot daschaa/powertools-lambda-typescript-fork
2 participants
@dreamorosi @daschaa