* Added “workflows” category for audit log * Fixed table * Updated links * Small edits * Added versioning * Added entry for `self_hosted_runner_updated` * Added repo entry for `self_hosted_runner_updated` * Added `enterprise` category actions * Added "starting_workflow_job" * Update reviewing-the-audit-log-for-your-organization.md * Added changes to security hardening guide * Update security-hardening-for-github-actions.md * Added versioning for "self-hosted runners" tables * Update reviewing-the-audit-log-for-your-organization.md * Apply suggestions from code review Co-authored-by: Sarah Edwards <skedwards88@github.com> * Update security-hardening-for-github-actions.md * Update reviewing-the-audit-log-for-your-organization.md * Update reviewing-the-audit-log-for-your-organization.md * Update security-hardening-for-github-actions.md * Update reviewing-the-audit-log-for-your-organization.md * Update security-hardening-for-github-actions.md * Update security-hardening-for-github-actions.md * Update reviewing-the-audit-log-for-your-organization.md * Update security-hardening-for-github-actions.md * Update reviewing-the-audit-log-for-your-organization.md * Update reviewing-the-audit-log-for-your-organization.md * Update security-hardening-for-github-actions.md * Moved enterprise events into reusable * Added versioning to exclude AE * Changed table identation and naming for consistency with reusable * Update security-hardening-for-github-actions.md * Update reviewing-the-audit-log-for-your-organization.md * Added note to mention that certain events can only be viewed using the API. * Added event visibility information. * Removed superfluous description text * Fixed typo * Moved table into reusable * Removed unused events superseded by `runner_group_updated` Co-authored-by: Sarah Edwards <skedwards88@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 %}.