7b142730bf
* Mention dependency files update for Gradle * Adding more specific caveats of apply support. Co-authored-by: Mike McDonald <2575327+asciimike@users.noreply.github.com> * Adding ip_allow_list entries I've added the ip_allow_list and ip_allow_list_entry category actions * Update backing-up-a-repository.md Add Azure Blob Storage as potential backup or storage service to have more options and especially also call out a non-consumer service with SLAs. * Add missing "Open Git Bash" step * Update data/reusables/dependabot/supported-package-managers.md * Update about-linked-identities.md * Update viewing-and-managing-a-members-saml-access-to-your-organization.md * Update viewing-and-managing-a-users-saml-access-to-your-enterprise.md * Fix workflow command for toolkit function (#10249) * fixed typographical errors * Update CONTRIBUTING.md * Fixed typographical errors * Apply suggestions from code review * Add 💅 * Move mention of SCIM * Add newline * Add Further Reading Links Fixes github#9906 * Fix link * Add Further Reading Links Fixes github#9906 * 🔀 linking Fixes github#9906 * 🔀 linking * 🔀 linking * Added further reading section * Update content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> * Update content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> * Update content/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization.md * Apply suggestions from code review * Update device flow OAuth app responses (#10426) Co-authored-by: Zbynek Konecny <zbynek1729@gmail.com> Co-authored-by: Mike McDonald <2575327+asciimike@users.noreply.github.com> Co-authored-by: Jonathan Cardona <Hollywood@github.com> Co-authored-by: Gerwald Oberleitner <gerwaldo@users.noreply.github.com> Co-authored-by: Rob Cowsill <42620235+rcowsill@users.noreply.github.com> Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Co-authored-by: Andre Kolodochka <59625655+andrekolodochka@users.noreply.github.com> Co-authored-by: Lee Dohm <1038121+lee-dohm@users.noreply.github.com> Co-authored-by: Abshar Mohammed Aslam <Absharaslam2001@gmail.com> Co-authored-by: Lulu <oluchi@lulunwenyi.com> Co-authored-by: Oluchi Nwenyi <dev@lulunwenyi.com> Co-authored-by: Ramya Parimi <ramyaparimi@github.com> Co-authored-by: James M. Greene <JamesMGreene@github.com> Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> Co-authored-by: Laura Coursen <lecoursen@github.com> Co-authored-by: PSJ <51746608+thispsj@users.noreply.github.com> Co-authored-by: Janice <janiceilene@github.com> Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com>
Reusables
Reusables are long strings of reusable text.
Reusables are longer strings like paragraphs or procedural lists that can be referenced in multiple content files. Using Markdown (instead of YAML) makes it possible for our localization pipeline to split the strings into smaller translatable segments, leading to fewer translation errors and less churn when the source English content changes.
Each reusable lives in its own Markdown file.
The path and filename of each Markdown file determines what its path will be in the data object.
For example, a file named /data/reusables/foo/bar.md will be accessible as {% data reusables.foo.bar %} in pages.
Reusable files are divided generally into directories by task. For example, if you're creating a reusable string for articles about GitHub notifications, you'd add it in the directory data/reusables/notifications/ in a file named data/reusables/notifications/your-reusable-name.md. The content reference you'd add to the source would look like {% data reusables.notifications.your-reusable-name %}.