Updated GitHub Actions template documentation

Author: rimi-itk

docs/github-actions-templates.md

@@ -1,6 +1,6 @@
 <!-- DO NOT EDIT THIS FILE!
 
-It was automatically created by task/scripts/github-documentation-update at Tue Apr  8 10:14:32 CEST 2025.
+It was automatically created by task/scripts/github-documentation-update at Tue Apr  8 13:30:36 CEST 2025.
 -->
 # Github Actions templates
 
@@ -11,8 +11,14 @@ to match the new templates.
 
 ## Naming conventions
 
-* Named after what a tool is concerned with, not how it's concerned with it.
-* Some configuration based on template type (drupal, symfony)
+* A workflow file is named after what it is _concerned_ with, not _how_ it's concerned with it and which tools are
+  actually used, i.e. we have a [`markdown.yaml`](github/workflows/markdown.yaml) file and not a `markdownlint.yaml`
+  file.
+* Some workflows are specific to a project type, currently `drupal` or `symfony`, and these sit in a project type
+  subfolder, e.g. `github/workflows/drupal`.
+* Some tools require configuration files, and these sit in the `config` folder. Some tool configuration may be specific
+  to a project type (or make sence only for a specific project type), and these specific config files sit in a project
+  type subfolder, e.g. `config/drupal/php/.phpcs.xml.dist` and `config/drupal/twig/.twig-cs-fixer.dist.php`
 
 ## Templates
 

task/templates/github-actions-templates.md

@@ -7,8 +7,14 @@ to match the new templates.
 
 ## Naming conventions
 
-* Named after what a tool is concerned with, not how it's concerned with it.
-* Some configuration based on template type (drupal, symfony)
+* A workflow file is named after what it is _concerned_ with, not _how_ it's concerned with it and which tools are
+  actually used, i.e. we have a [`markdown.yaml`](github/workflows/markdown.yaml) file and not a `markdownlint.yaml`
+  file.
+* Some workflows are specific to a project type, currently `drupal` or `symfony`, and these sit in a project type
+  subfolder, e.g. `github/workflows/drupal`.
+* Some tools require configuration files, and these sit in the `config` folder. Some tool configuration may be specific
+  to a project type (or make sence only for a specific project type), and these specific config files sit in a project
+  type subfolder, e.g. `config/drupal/php/.phpcs.xml.dist` and `config/drupal/twig/.twig-cs-fixer.dist.php`
 
 ## Templates