Adding an action to your workflow
You can add an action to your workflow by referencing the action in your workflow file. The actions you use in your workflow can be defined in:
[F] The same repository as your workflow file
[C] Any public repository
[B] A published Docker container image on Docker Hub
Note: Adding an action from the same repository [F]
If an action is defined in the same repository where your workflow file uses the action, you can reference the action with either the {owner}/{repo}@{ref} or ./path/to/dir syntax in your workflow file.
Reference:
https://docs.github.com/en/actions/how-tos/write-workflows/choose-what-workflows-do/find-and- customize-actions

A custom GitHub Action's inputs, outputs, and other configurations are defined in its metadata file, which must be named action.yml or action.yaml and placed at the root of the action's repository. This YAML file specifies how the action runs (e.g., using Docker or JavaScript) and provides the metadata for its inputs and outputs, which are then used by workflows that call the action.
Key aspects of the action.yml or action.yaml file
Format: It uses YAML syntax.
Location: It must be in the root directory of your action's repository.
Contents: It defines the action's name, description, inputs, outputs, and the runs configuration to specify the execution environment (like a Docker image or JavaScript file) and entrypoint.
Inputs and Outputs: The file includes inputs and outputs sections to declare the data the action accepts and produces, respectively.
Reference:
https://docs.github.com/en/actions/reference/workflows-and-actions/metadata-syntax

[D] Encrypted secrets can be accessed across repositories in the same organization, making it easy to store sensitive data (like API keys or tokens) securely while allowing multiple workflows to access them.
[E] Workflow templates allow you to create reusable templates for workflows that can be shared across repositories within the organization. This makes it easier to standardize processes and automate them across multiple projects.
[F] Actions stored in private repositories within the organization can be reused across all repositories by referencing them in workflows. This ensures a centralized way of maintaining custom actions.
Reference:
https://docs.github.com/en/actions/how-tos/reuse-automations/reuse-workflows

The correct options are name: release-flow-42 and name: ${{ 'release-flow-42' }}. Both set the workflow name that appears in the Actions interface and on the workflow page.
The plain static name key with a simple string sets the workflow name clearly and predictably. It is the most straightforward way to define the workflow title.
The expression form with a single quoted string evaluates to the same literal value. GitHub Actions accepts a string result for the workflow name, so this produces a valid name while keeping consistency with other places where expressions are used.

Deleting a workflow run
You can delete a workflow run that has been completed, or is more than two weeks old.
Reference:
https://docs.github.com/en/enterprise-cloud@latest/actions/how-tos/manage-workflow- runs/delete-a-workflow-run