|
| 1 | +# pullRequests.frequency allows to control how often or when Scala Steward |
| 2 | +# is allowed to create pull requests. |
| 3 | +# |
| 4 | +# Possible values: |
| 5 | +# @asap |
| 6 | +# PRs are created without delay. |
| 7 | +# |
| 8 | +# <timespan> |
| 9 | +# PRs are created only again after the given timespan since the last PR |
| 10 | +# has passed. Example values are "36 hours", "1 day", or "14 days". |
| 11 | + |
| 12 | +# <CRON expression> |
| 13 | +# PRs are created roughly according to the given CRON expression. |
| 14 | +# |
| 15 | +# CRON expressions consist of five fields: |
| 16 | +# minutes, hour of day, day of month, month, and day of week. |
| 17 | +# |
| 18 | +# See https://www.alonsodomin.me/cron4s/userguide/index.html#parsing for |
| 19 | +# more information about the CRON expressions that are supported. |
| 20 | +# |
| 21 | +# Note that the date parts of the CRON expression are matched exactly |
| 22 | +# while the time parts are only used to abide to the frequency of |
| 23 | +# the given expression. |
| 24 | +# |
| 25 | +# Default: @asap |
| 26 | +# |
| 27 | +#pullRequests.frequency = "0 0 ? * 3" # every thursday on midnight |
| 28 | +pullRequests.frequency = "7 days" |
| 29 | + |
| 30 | +# pullRequests.grouping allows you to specify how Scala Steward should group |
| 31 | +# your updates in order to reduce the number of pull-requests. |
| 32 | +# |
| 33 | +# Updates will be placed in the first group with which they match, starting |
| 34 | +# from the first in the array. Those that do not match any group will follow |
| 35 | +# the default procedure (one PR per update). |
| 36 | +# |
| 37 | +# Each element in the array will have the following schema: |
| 38 | +# |
| 39 | +# - name (mandatory): the name of the group, will be used for things like naming the branch |
| 40 | +# - title (optional): if provided it will be used as the title for the PR |
| 41 | +# - filter (mandatory): a non-empty list containing the filters to use to know |
| 42 | +# if an update falls into this group. |
| 43 | +# |
| 44 | +# `filter` properties would have this format: |
| 45 | +# |
| 46 | +# { |
| 47 | +# version = "major" | "minor" | "patch" | "pre-release" | "build-metadata", |
| 48 | +# group = "{group}", |
| 49 | +# artifact = "{artifact}" |
| 50 | +# } |
| 51 | +# |
| 52 | +# For more information on the values for the `version` filter visit https://semver.org/ |
| 53 | +# |
| 54 | +# Every field in a `filter` is optional but at least one must be provided. |
| 55 | +# |
| 56 | +# For grouping every update togeher a filter like {group = "*"} can be # provided. |
| 57 | +# |
| 58 | +# Default: [] |
| 59 | +pullRequests.grouping = [ |
| 60 | + { name = "patches", "title" = "Patch updates", "filter" = [{"version" = "patch"}] }, |
| 61 | + { name = "minor_major", "title" = "Minor/major updates", "filter" = [{"version" = "minor"}, {"version" = "major"}] }, |
| 62 | + { name = "cats", "title" = "Cats ecosystem updates", "filter" = [{"group" = "org.typelevel"}, {"group" = "org.http4s"}, {"group" = "io.circe"}] }, |
| 63 | + { name = "all", title = "Dependency updates", "filter" = [{"group" = "*"}] } |
| 64 | +] |
0 commit comments