Skip to content

Commit b505f6f

Browse files
committed
Fix formatting issues in doc
1 parent 5c1ac4b commit b505f6f

1 file changed

Lines changed: 7 additions & 6 deletions

File tree

  • doc/user_guide/features/github_workflows

doc/user_guide/features/github_workflows/index.rst

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -112,12 +112,13 @@ When configured as described on :ref:`github_project_configuration`, the
112112
workflows, like ``slow-checks.yml``. This allows developers to update their pull
113113
request more often and to only periodically run the more time-expensive tests.
114114

115-
The `report.yml` is called twice:
116-
#. after the steps in `checks.yml` successfully finish - this allows developers
117-
to get faster feedback for linting, security, and unit test coverage.
118-
#. after the steps in `slow-checks.yml` successfully finish - this gives developers an
119-
overview of the total coverage, as well as the information provided from running
120-
the `checks.yml`
115+
The ``report.yml`` is called twice:
116+
117+
#. after the steps in ``checks.yml`` successfully finish - this allows developers
118+
to get faster feedback for linting, security, and unit test coverage.
119+
#. after the steps in ``slow-checks.yml`` successfully finish - this gives developers an
120+
overview of the total coverage, as well as the information provided from running
121+
the ``checks.yml``
121122

122123
In both scenarios, the results are posted in the PR and made available on Sonar's UI.
123124
Note that Sonar does not keep historical information, so it will only show the latest

0 commit comments

Comments
 (0)