t.behrendt/renovate-configs
1
0
Fork 0
Code Issues 6 Pull Requests Actions Releases Activity

feat(common): add best-practices #16

Merged
t.behrendt merged 1 commits from feat-add-best-practices into main 2025-11-08 22:32:02 +01:00
Conversation 2 Commits 1 Files Changed 1 +2 -1
t.behrendt commented 2025-11-08 22:31:17 +01:00
Owner
Copy Link
No description provided.
t.behrendt added 1 commit 2025-11-08 22:31:18 +01:00
feat(common): add best-practices
All checks were successful
CI / Test (common.json) (pull_request) Successful in 16s
Details
CI / Test (docker-compose.json) (pull_request) Successful in 14s
Details
CI / Test (helm.json) (pull_request) Successful in 14s
Details
CI / Test (k8s.json) (pull_request) Successful in 14s
Details
CI / Test (action.json) (pull_request) Successful in 38s
Details
337578188e
t.behrendt requested review from branch-buddy 2025-11-08 22:31:23 +01:00
branch-buddy approved these changes 2025-11-08 22:31:38 +01:00
Dismissed
branch-buddy left a comment
Collaborator
Copy Link

The changes align with the PR title, adding best-practices configuration by extending 'config:best-practices'. JSON syntax is correct, and no obvious issues were found.

The changes align with the PR title, adding best-practices configuration by extending 'config:best-practices'. JSON syntax is correct, and no obvious issues were found.
branch-buddy approved these changes 2025-11-08 22:31:49 +01:00
branch-buddy left a comment
Collaborator
Copy Link

The changes align with the PR title, adding best practices configuration via 'extends': ['config:best-practices'] in common.json. No obvious issues found in the diff.

The changes align with the PR title, adding best practices configuration via 'extends': ['config:best-practices'] in common.json. No obvious issues found in the diff.
t.behrendt scheduled this pull request to auto merge when all checks succeed 2025-11-08 22:31:58 +01:00
t.behrendt merged commit 3610c5de66 into main 2025-11-08 22:32:02 +01:00
t.behrendt deleted branch feat-add-best-practices 2025-11-08 22:32:02 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
branch-buddy
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
branch-buddy renovate-bot t.behrendt
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: t.behrendt/renovate-configs#16
Delete Branch "feat-add-best-practices"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?