docs/data/variables
Matt Pollard 19c8b713a2
Add release candidate banner for GitHub Enterprise Server 3.8 (#34518)
2023-02-07 18:31:14 +00:00
..
README.md
actions.yml revised diagram, added variable for product name 2022-08-22 14:27:56 +10:00
code-scanning.yml Improve comments for code security variables (#32445) 2022-11-11 09:31:37 +00:00
codespaces.yml Add info on using github.dev behind a firewall (#33184) 2022-12-14 15:37:59 +00:00
command_line.yml Update styling for placeholder text 2022-11-18 16:02:31 -05:00
contact.yml Rename github-community to community 2022-07-27 17:36:23 -04:00
dependency-review.yml Move variable relating to Dependency Review outside the `product.yml` file (#33443) 2022-12-12 15:13:44 +00:00
desktop.yml
enterprise.yml GitHub Enterprise Server 3.7 release candidate (#31313) 2022-10-25 18:35:59 +02:00
explore.yml
gists.yml
large_files.yml
location.yml Updating error message for OpenAPI Descriptions check (#31720) 2022-10-17 19:35:34 +00:00
migrations.yml Unify API terminology around 'REST API' for Migrations content (#33672) 2023-01-03 16:27:05 +00:00
notifications.yml
product.yml [DO NOT MERGE] GitHub Enterprise Server 3.8 release candidate (#34113) 2023-02-07 17:49:44 +00:00
projects.yml [DO NOT MERGE] GitHub Enterprise Server 3.8 release candidate (#34113) 2023-02-07 17:49:44 +00:00
release_candidate.yml Add release candidate banner for GitHub Enterprise Server 3.8 (#34518) 2023-02-07 18:31:14 +00:00
search.yml
secret-scanning.yml Create new yml file for secret scanning variables that aren't products (take 3) (#33609) 2022-12-16 10:02:43 +00:00
visual_studio.yml [2022-10-31] Visual Studio — remove anything that isn't a product name (#32119) 2022-10-31 10:45:43 +00:00

README.md

Variables

Variables are short strings of reusable text.

The YAML files in this directory each contain multiple variables.

The path, filename, and keys within each YAML file determine what its path will be in the data object.

For example, given a file data/variables/foo/bar.yml:

# multiple short strings in one file
meaning_of_life: 42

# and they can be nested if needed
nested:
  values:
    too: Yes!

Its values would be accessible as:

{% data foo.bar.meaning_of_life %}

{% data foo.bar.nested.values.too %}