Change Actions example table styling (#28772)
This commit is contained in:
@@ -7,7 +7,6 @@ versions:
|
||||
ghes: '>= 3.5'
|
||||
ghae: 'issue-4925'
|
||||
ghec: '*'
|
||||
showMiniToc: false
|
||||
type: how_to
|
||||
topics:
|
||||
- Workflows
|
||||
@@ -15,12 +14,6 @@ topics:
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
- [Example overview](#example-overview)
|
||||
- [Features used in this example](#features-used-in-this-example)
|
||||
- [Example workflow](#example-workflow)
|
||||
- [Understanding the example](#understanding-the-example)
|
||||
- [Next steps](#next-steps)
|
||||
|
||||
## Example overview
|
||||
|
||||
{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it tests your code using a matrix of test combinations with `npm test`.
|
||||
@@ -54,7 +47,7 @@ topics:
|
||||
|
||||
{% data reusables.actions.note-understanding-example %}
|
||||
|
||||
<table style="width:350px">
|
||||
<table style="table-layout: fixed;">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width:100%"></th>
|
||||
@@ -222,7 +215,7 @@ jobs:
|
||||
|
||||
{% data reusables.actions.example-explanation-table-intro %}
|
||||
|
||||
<table style="width:350px">
|
||||
<table style="table-layout: fixed;">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width:60%"><b>Code</b></th>
|
||||
|
||||
@@ -7,7 +7,6 @@ versions:
|
||||
ghes: '> 3.1'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
showMiniToc: false
|
||||
type: how_to
|
||||
topics:
|
||||
- Workflows
|
||||
@@ -15,12 +14,6 @@ topics:
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
- [Example overview](#example-overview)
|
||||
- [Features used in this example](#features-used-in-this-example)
|
||||
- [Example workflow](#example-workflow)
|
||||
- [Understanding the example](#understanding-the-example)
|
||||
- [Next steps](#next-steps)
|
||||
|
||||
## Example overview
|
||||
|
||||
{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links.
|
||||
@@ -52,7 +45,7 @@ topics:
|
||||
|
||||
{% data reusables.actions.note-understanding-example %}
|
||||
|
||||
<table style="width:350px">
|
||||
<table style="table-layout: fixed;">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width:100%"></th>
|
||||
@@ -140,7 +133,7 @@ jobs:
|
||||
|
||||
{% data reusables.actions.example-explanation-table-intro %}
|
||||
|
||||
<table style="width:350px">
|
||||
<table style="table-layout: fixed;">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width:60%"><b>Code</b></th>
|
||||
|
||||
@@ -7,7 +7,6 @@ versions:
|
||||
ghes: '> 3.1'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
showMiniToc: false
|
||||
type: how_to
|
||||
topics:
|
||||
- Workflows
|
||||
@@ -15,12 +14,6 @@ topics:
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
- [Example overview](#example-overview)
|
||||
- [Features used in this example](#features-used-in-this-example)
|
||||
- [Example workflow](#example-workflow)
|
||||
- [Understanding the example](#understanding-the-example)
|
||||
- [Next steps](#next-steps)
|
||||
|
||||
## Example overview
|
||||
|
||||
{% data reusables.actions.example-workflow-intro-ci %} When this workflow is triggered, it automatically runs a script that checks whether the {% data variables.product.prodname_dotcom %} Docs site has any broken links. If any broken links are found, the workflow uses the {% data variables.product.prodname_dotcom %} CLI to create a {% data variables.product.prodname_dotcom %} issue with the details.
|
||||
@@ -54,7 +47,7 @@ topics:
|
||||
|
||||
{% data reusables.actions.note-understanding-example %}
|
||||
|
||||
<table style="width:350px">
|
||||
<table style="table-layout: fixed;">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width:70%"></th>
|
||||
@@ -185,7 +178,7 @@ jobs:
|
||||
|
||||
{% data reusables.actions.example-explanation-table-intro %}
|
||||
|
||||
<table style="width:350px">
|
||||
<table style="table-layout: fixed;">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width:60%"><b>Code</b></th>
|
||||
|
||||
@@ -219,3 +219,19 @@ You can define a default tool in the frontmatter. For more information, see the
|
||||
Reusable strings (commonly called content references or conrefs) contain content that’s used in more than one place in our documentation and allow us to change the content in a single location rather than every place the string appears.
|
||||
|
||||
For longer strings, we use reusables, and for shorter strings, we use variables. For more information about reusables, see the [reusables README](../data/reusables/README.md). For more information about variables, see the [variables README](../data/variables/README.md).
|
||||
|
||||
## Tables with codeblocks
|
||||
|
||||
Although using tables to contain block items, such as code blocks, is generally discouraged, occasionally it may be appropriate.
|
||||
|
||||
Because [tables in GitHub Flavored Markdown](https://github.github.com/gfm/#tables-extension-) cannot contain any line breaks or block-level structures, you must use HTML tags to write the table structure.
|
||||
|
||||
When HTML tables contain code blocks, the width of the table might exceed the regular width of page content, and then overflow into the area normally containing the mini table of contents.
|
||||
|
||||
If this happens, add the following CSS style to the `<table>` HTML tag:
|
||||
|
||||
```html
|
||||
<table style="table-layout: fixed;">
|
||||
```
|
||||
|
||||
For a current example of this usage, see the [GitHub Actions examples workflow library](https://docs.github.com/en/actions/examples).
|
||||
|
||||
Reference in New Issue
Block a user