Skip to content

Clarify multi-select config group docs#3249

Merged
omry merged 1 commit into
mainfrom
pr3249
Jun 30, 2026
Merged

Clarify multi-select config group docs#3249
omry merged 1 commit into
mainfrom
pr3249

Conversation

@omry

@omry omry commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator

Reduce the multi-select example to focus on selecting multiple configs from one config group. Remove the extra apache_https server option and use a direct server/apache include in the example config.

Clarify that the nested list form composes like expanded config entries while preserving group override syntax, and fix the delete example path.

Closes #2695.

Copilot AI review requested due to automatic review settings June 30, 2026 04:01
@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jun 30, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates Hydra’s “Selecting multiple configs from a Config Group” documentation and the linked examples/patterns/multi-select example to better focus on multi-select behavior within a single config group, and to correct/clarify override and deletion syntax discussed in #2695.

Changes:

  • Clarifies how nested-list defaults relate to explicit defaults entries, and fixes the delete-path example in the docs.
  • Simplifies the example by removing the extra apache_https server option and switching the example root config to a direct server/apache include.
  • Aligns the example configuration syntax with what the docs describe.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File Description
website/docs/patterns/select_multiple_configs_from_config_group.md Clarifies composition semantics for nested lists and fixes the CLI delete-path example.
examples/patterns/multi-select/conf/server/apache_https.yaml Removes the extra server option from the example configuration set.
examples/patterns/multi-select/conf/config.yaml Switches the example defaults entry to a direct server/apache include.

Comment on lines 1 to +2
defaults:
- server: apache
- server/apache
Comment on lines +149 to +150
A nested list in the Defaults List is interpreted as a list of non-overridable
configs. The following two forms compose the same output:
Comment thread website/docs/patterns/select_multiple_configs_from_config_group.md Outdated
### Implementation considerations

A nested list in the Defaults List is interpreted as a list of non-overridable configs:
A nested list in the Defaults List is interpreted as a list of non-overridable

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

### Implementation considerations

A nested list in the Defaults List is interpreted as a list of non-overridable configs:
The following two forms compose the same output:
Comment on lines +132 to +136
Use the nested list form when you want to override the group later with
`server/site=[...]`.

To delete one of these non-overridable entries from the command line, use the
exact config path, for example `~site/fb`.
exact config path, for example `~server/site/fb`.
Reduce the multi-select example to focus on selecting multiple configs from one config group. Remove the extra apache_https server option and use a direct server/apache include in the example config.

Clarify that the nested list form composes like expanded config entries while preserving group override syntax, and fix the delete example path.

Closes #2695.
@omry omry merged commit fcdf7e9 into main Jun 30, 2026
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Confusing description in "Selecting multiple configs from a Config Group"

2 participants