function of branch key in server-side config

[cosmo-grant]

The atlantis docs describe the branch key as follows:

An regex matching pull requests by base branch (the branch the pull request is getting merged into). By default, all branches are matched

Does this mean (a) that atlantis will ignore the config for base branches which don't match the branch regex, or (b) that atlantis will ignore pull requests for base branches which don't match the branch regex?

In other words, does branch restrict the scope of the config, or restrict the scope of atlantis?

For example:

# repos.yaml
repos:
- id: github.com/runatlantis/atlantis
  branch: /main/
  apply_requirements: [approved]

This means a pr into main will need to be approved before the plan can be applied.

My question is: For a pr into other_branch, will atlantis ignore the pr, or will it just ignore the config?

[nitrocode]

For a pr into other_branch, will atlantis ignore the pr, or will it just ignore the config?

It will ignore other_branch because it is only set to match on main

[cosmo-grant]

Thank you