kjuulh/char
1
0
Fork 0
Code Issues 1 Pull Requests 3 Packages Projects Releases Wiki Activity

Configure Renovate #1

Merged
kjuulh merged 1 commits from renovate/configure into main 2022-11-05 23:33:30 +01:00
Conversation 0 Commits 1 Files Changed 1 +3
kjuulh commented 2022-11-01 19:20:58 +01:00
Owner
Copy Link

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

  • go.mod (gomod)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Enable Renovate Dependency Dashboard creation.
  • If Renovate detects semantic commits, it will use semantic commit type fix for dependencies and chore for all others.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Autodetect whether to pin dependencies or maintain ranges.
  • Rate limit PR creation to a maximum of two per hour.
  • Limit to maximum 10 open PRs at any time.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • A collection of workarounds for known problems with packages.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

Update all dependencies

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR has been generated by Renovate Bot.

Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged. --- ### Detected Package Files * `go.mod` (gomod) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding PR is merged - Enable Renovate Dependency Dashboard creation. - If Renovate detects semantic commits, it will use semantic commit type `fix` for dependencies and `chore` for all others. - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories. - Autodetect whether to pin dependencies or maintain ranges. - Rate limit PR creation to a maximum of two per hour. - Limit to maximum 10 open PRs at any time. - Group known monorepo packages together. - Use curated list of recommended non-monorepo package groupings. - A collection of workarounds for known problems with packages. 🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the `renovate.json` in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs. --- ### What to Expect With your current configuration, Renovate will create 1 Pull Request: <details> <summary>Update all dependencies</summary> - Schedule: ["at any time"] - Branch name: `renovate/all` - Merge into: `main` - Upgrade [github.com/hashicorp/go-hclog](https://github.com/hashicorp/go-hclog) to `v1.3.1` - Upgrade [golang.org/x/sync](https://github.com/golang/sync) to `8fcdb60fdcc0539c5e357b2308249e4e752147f1` </details> --- ❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
kjuulh force-pushed renovate/configure from bb99d65591 to e560e137c4 2022-11-02 21:06:12 +01:00 Compare
kjuulh force-pushed renovate/configure from e560e137c4 to a9e0b55e98 2022-11-02 22:15:13 +01:00 Compare
kjuulh force-pushed renovate/configure from a9e0b55e98 to f2a30f5c2e 2022-11-02 23:03:47 +01:00 Compare
kjuulh force-pushed renovate/configure from f2a30f5c2e to 8e46468ea7 2022-11-02 23:19:01 +01:00 Compare
kjuulh force-pushed renovate/configure from 8e46468ea7 to 5c26466e67 2022-11-05 23:10:56 +01:00 Compare
kjuulh force-pushed renovate/configure from 5c26466e67 to d7bfd941ae 2022-11-05 23:26:34 +01:00 Compare
kjuulh merged commit 1e5d4eda11 into main 2022-11-05 23:33:30 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kjuulh/char#1
No description provided.
Delete Branch "renovate/configure"

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?