Add docs on rules

docs/configuration/allow_security_updates_on_concurrent_limit.mdx

@@ -24,6 +24,7 @@ title: "allow_security_updates_on_concurrent_limit"
 
 Indicates if you want to allow security updates when the concurrent limit is reached, in addition to your open merge requests.
 
+> **Note:** This option is **root project only** and cannot be used within [rules](/configuration/rules). It modifies the global `number_of_concurrent_updates` behavior.
 
 ## Explanation
 

docs/configuration/allow_updates_beyond_constraint.mdx

@@ -25,6 +25,8 @@ weight:
 
 Indicate whether or not we can try to update a package even if it is beyond the range specified in composer.json. Defaults to 1 (true).
 
+> **Note:** This option can be used within [rules](/configuration/rules) to allow constraint-breaking updates for some package groups while preventing them for others.
+
 ## Explanation
 
 Strictly speaking, if your composer.json specifies that you want to have the package `vendor/package` in the version range `~1.0.0`, then composer will install all version in the range 1.0.x, but refuse to update it to 1.1.0. Some times this is what you want. But many times, a new version at 1.1.0 will include new features and be backwards compatible. So maybe you actually might want to start using that version instead? This is what the option for allowing to update beyond your version constraint does.

docs/configuration/always_update_all.mdx

@@ -25,6 +25,8 @@ weight:
 
 Indicate if you always want violinist to update all packages (simply the command `composer update` with no arguments) every time it runs.
 
+> **Note:** This option is **root project only** and cannot be used within [rules](/configuration/rules). This update strategy is incompatible with package-specific rules since it updates all packages together.
+
 ## Explanation
 
 This is probably most useful if you have not so many dependencies, or if you are replacing a manual workflow that involves running `composer update` on a regular basis. If you are using this option, only one pull request will be created by violinist, and it will contain the updates that would happen if you were running `composer update`. So this option updates all of your dependencies, all of the time.

docs/configuration/assignees.mdx

@@ -27,6 +27,8 @@ weight:
 
 An array of assignees that this project will use as the default assignee for new pull requests.
 
+> **Note:** This option can be used within [rules](/configuration/rules) to assign different package groups to different team members or teams.
+
 >Note! The value of this option depends on your VCS provider. For github this will be an array of usernames. For gitlab the array should consist of user IDs. You can find your user id by visiting [https://gitlab.com/api/v4/users?username=YOUR_USERNAME](https://gitlab.com/api/v4/users?username=YOUR_USERNAME) where YOUR_USERNAME is your gitlab username. (reference: [https://forum.gitlab.com/t/where-is-my-user-id-in-gitlab-com/7912](https://forum.gitlab.com/t/where-is-my-user-id-in-gitlab-com/7912))
 >
 >If you are using self hosted gitlab, change the domain accordingly.

docs/configuration/automerge.mdx

@@ -25,6 +25,8 @@ weight:
 
 Indicate whether or not you want pull/merge requests created by violinist to have the automerge option enabled.
 
+> **Note:** This option can be used within [rules](/configuration/rules) to enable automerge for specific package groups while keeping it disabled for others.
+
 > Note! This option currently does not work with Bitbucket.
 
 ## Explanation

docs/configuration/automerge_method.mdx

@@ -23,6 +23,8 @@ title: "automerge_method"
 
 Indicates which merge method should be used when using [automerge](/configuration/automerge).
 
+> **Note:** This option can be used within [rules](/configuration/rules) to set different merge methods for different package groups.
+
 > Note! This option currently does not work with Bitbucket.
 
 ## Explanation

docs/configuration/automerge_method_security.mdx

@@ -23,6 +23,8 @@ title: "automerge_method_security"
 
 Indicates which merge method should be used when using [automerge](/configuration/automerge). But in contrast to the [automerge_method](/configuration/automerge_method) option, this will allow you to have a separate method for security updates.
 
+> **Note:** This option can be used within [rules](/configuration/rules) to set different security merge methods for different package groups.
+
 > Note! This option currently does not work with Bitbucket.
 
 ## Explanation

docs/configuration/automerge_security.mdx

@@ -25,6 +25,8 @@ weight:
 
 Indicate whether or not you want pull/merge requests created by violinist to have the automerge option enabled when the update is a security update.
 
+> **Note:** This option can be used within [rules](/configuration/rules) to enable security automerge for specific package groups.
+
 > Note! This option currently does not work with Bitbucket.
 
 > Note! This option only overrides the automerge option if the update is a security update. If `automerge_security` is set to `0`, but `automerge` is set to `1`, then automerge will be enabled.