Add option to playbook to configure default branch pattern(s)
Add a new option to the playbook for configuring the default branch pattern or patterns. This information will be used by the content aggregator to know which branches of a VCS repository (e.g., git repository) to use if no branches are specified for that entry.
The proposed location in the playbook for this option is as follows*:
content: branches: v*
* I'm also considering the name
defaultBranches instead of
The configuration property should accept either a string (e.g.,
v*) or an array of strings (e.g.,
It may seem strange to configure the default branches under
content when there may be sources in the future that are not git repositories. However, I don't think we want to overthink it.
If this option is not specified, the default should be
['v*', 'master']. That value accommodates convention over configuration.