The name key can be used to invoke reusable jobs across any number of workflows.
Using the name key ensures numbers are not appended to your job name (i.e. sayhello-1,
sayhello-2, etc.).
The name you assign to the name key needs to be unique, otherwise the numbers will still be
appended to the job name.
A list of jobs that must succeed for the job to start.
Note: When jobs in the current workflow that are listed as dependencies are not executed
(due to a filter function for example), their requirement as a dependency for other jobs will
be ignored by the requires option.
However, if all dependencies of a job are filtered, then that job will not be executed either.
Jobs may be configured to use global environment variables set for an organization, see the
Contexts document for adding a context in the
application settings.
The initial default name is org-global.
Each context name must be unique.
If using CircleCI Server, only a single Context per workflow is supported.
Note: A maximum of 100 unique contexts across all workflows is allowed
The name key can be used to invoke reusable jobs across any number of workflows.