Merge branch '327315-enable-ci_wildcard_file_paths' into 'master'

Enable the FF ci_wildcard_file_paths by default

See merge request gitlab-org/gitlab!61507

changelogs/unreleased/327315-enable-ci_wildcard_file_paths.yml

+---
+title: Implement wildcard support for pipeline include file paths
+merge_request: 61507
+author:
+type: added

config/feature_flags/development/ci_wildcard_file_paths.yml

@@ -5,4 +5,4 @@ rollout_issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/327315
 milestone: '13.11'
 type: development
 group: group::pipeline authoring
-default_enabled: false
+default_enabled: true

doc/ci/yaml/README.md

@@ -482,10 +482,15 @@ Use local includes instead of symbolic links.
 ##### `include:local` with wildcard file paths
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/25921) in GitLab 13.11.
-> - It's [deployed behind a feature flag](../../user/feature_flags.md), disabled by default.
-> - It's disabled on GitLab.com.
-> - It's not recommended for production use.
-> - To use it in GitLab self-managed instances, ask a GitLab administrator to enable it. **(CORE ONLY)**
+> - [Deployed behind a feature flag](../../user/feature_flags.md), disabled by default.
+> - [Enabled by default](https://gitlab.com/gitlab-org/gitlab/-/issues/327315) in GitLab 13.12.
+> - Enabled on GitLab.com.
+> - Recommended for production use.
+> - For GitLab self-managed instances, GitLab administrators can opt to disable it. **(CORE ONLY)**
+
+There can be
+[risks when disabling released features](../../user/feature_flags.md#risks-when-disabling-released-features).
+Refer to this feature's version history for more details.
 
 You can use wildcard paths (`*` and `**`) with `include:local`.
 
@@ -509,10 +514,10 @@ When the pipeline runs, GitLab:
   include: 'configs/**/*.yml'
   ```
 
-The wildcard file paths feature is under development and not ready for production use. It is
-deployed behind a feature flag that is **disabled by default**.
+The wildcard file paths feature is under development but ready for production use.
+It is deployed behind a feature flag that is **enabled by default**.
 [GitLab administrators with access to the GitLab Rails console](../../administration/feature_flags.md)
-can enable it.
+can opt to disable it.
 
 To enable it: