Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix danger alert #35443

Merged
merged 2 commits into from
Nov 27, 2024
Merged

Fix danger alert #35443

merged 2 commits into from
Nov 27, 2024

Conversation

akordowski
Copy link
Contributor

Why:

The danger alert does not match other alerts.

Closes: #35435

What's being changed (if available, include any code snippets, screenshots, or gifs):

The danger alert has been changed to the > [!CAUTION] markdown notation.

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Nov 27, 2024
Copy link
Contributor

github-actions bot commented Nov 27, 2024

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.


Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
admin/monitoring-and-managing-your-instance/configuring-clustering/monitoring-the-health-of-your-cluster.md ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
admin/configuring-settings/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
from reusable
admin/monitoring-and-managing-your-instance/configuring-clustering/cluster-network-configuration.md ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
from reusable

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

@nguyenalex836 nguyenalex836 added content This issue or pull request belongs to the Docs Content team administering a repo Content relating to administering a repo and removed triage Do not begin working on this issue until triaged by the team labels Nov 27, 2024
@nguyenalex836 nguyenalex836 added this pull request to the merge queue Nov 27, 2024
Merged via the queue into github:main with commit 27a19de Nov 27, 2024
44 checks passed
Copy link
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
administering a repo Content relating to administering a repo content This issue or pull request belongs to the Docs Content team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Align danger alert to match the markdown notation
2 participants