What is the exact file path and file extension for a GitHub Actions workflow definition file within a repository?

A GitHub Actions workflow definition file must reside within a specific directory structure inside a repository. The exact file path begins from the root of the repository, followed by a hidden directory named `.github`, then a subdirectory named `workflows`. The file extension for these files must be either `.yml` or `.yaml`. These two extensions are interchangeable and both signify that the file is formatted using YAML. Therefore, the complete and exact structural file path is `/.github/workflows/your-workflow-name.yml` or `/.github/workflows/your-workflow-name.yaml`. To elaborate, the `.github` directory is a special, top-level directory that GitHub automatically recognizes for various repository configurations and settings, including GitHub Actions. Within this `.github` directory, the `workflows` subdirectory is specifically designated to contain all workflow definition files. GitHub automatically scans this `workflows` subdirectory for any files that end with the `.yml` or `.yaml` extension, treating them as valid workflow definitions. YAML, which stands for YAML Ain't Markup Language, is a human-readable data serialization standard commonly used for configuration files. A workflow definition file itself is a YAML-formatted text file that contains a series of instructions, defining an automated process. This process specifies what steps GitHub Actions should take, such as building code, running tests, or deploying applications, and under what conditions these actions should be triggered, like a push to a specific branch or the creation of a pull request. The `your-workflow-name` component in the path is a user-defined filename that should describe the workflow's purpose, for example, `/.github/workflows/build-and-test.yml` or `/.github/workflows/deploy.yaml`.