Skip to content

Commit cef8b44

Browse files
committed
Remove horizontal rules
1 parent 6aedc30 commit cef8b44

5 files changed

Lines changed: 0 additions & 30 deletions

File tree

doc/explanation/vendoring.rst

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,6 @@ Vendoring does not necessarily imply permanent forks or heavy modification of
3232
third-party code. In many cases, vendored dependencies are kept pristine and
3333
updated mechanically from upstream sources.
3434

35-
----
36-
3735
.. div:: band-tint
3836

3937
:material-regular:`thumb_up;2em;sd-text-primary` **Why vendoring can be helpful**
@@ -73,8 +71,6 @@ updated mechanically from upstream sources.
7371
teams become **more selective** and more aware of the long-term cost of
7472
that decision.
7573

76-
----
77-
7874
.. div:: band-mint
7975

8076
:material-regular:`warning;2em;sd-text-primary` **The costs and risks of vendoring**
@@ -233,8 +229,6 @@ Conclusion
233229
Used intentionally and with an understanding of its limitations, vendoring is
234230
simply one tool among many for managing dependencies.
235231

236-
----
237-
238232
Best Practices
239233
--------------
240234

@@ -391,8 +385,6 @@ eliminate them.
391385
*Dfetch* enables this by allowing you to store the vendored dependency in a folder
392386
using the ``dst:`` attribute.
393387

394-
----
395-
396388
.. div:: band-tint
397389

398390
:material-regular:`public;2em;sd-text-primary` **Real-world projects using vendoring**

doc/howto/check-ci.rst

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,6 @@ own report format so findings surface natively inside the platform's UI.
1313
- :ref:`check-ci-github` — upload SARIF results to GitHub code scanning
1414
- :ref:`check-ci-gitlab` — publish code-quality reports in GitLab merge requests
1515

16-
----
17-
1816
.. _check-ci-run:
1917

2018
Running dfetch check in CI
@@ -35,8 +33,6 @@ Pass a ``--*-json`` flag to write a machine-readable report *and* continue
3533
collecting results before deciding the build outcome (each section below shows
3634
the exact flag).
3735

38-
----
39-
4036
.. _check-ci-jenkins:
4137

4238
Jenkins (warnings-ng)
@@ -90,8 +86,6 @@ the build fails — for example, allow pinned-out-of-date without failing.
9086
.. _`warnings-ng native JSON format`: https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#export-your-issues-into-a-supported-format
9187
.. _`quality gate configuration`: https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#quality-gate-configuration
9288

93-
----
94-
9589
.. _check-ci-github:
9690

9791
GitHub Actions (SARIF)
@@ -170,8 +164,6 @@ For more information see the `GitHub SARIF documentation`_.
170164

171165
.. _`GitHub SARIF documentation`: https://docs.github.com/en/code-security/code-scanning/integrating-with-code-scanning
172166

173-
----
174-
175167
.. _check-ci-gitlab:
176168

177169
GitLab CI (Code Climate)

doc/howto/patching.rst

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,6 @@ The full lifecycle looks like this:
1818
3. :ref:`patching-update` — refresh the patch as your edits evolve with ``dfetch update-patch``
1919
4. :ref:`patching-upstream` — reformat the patch for upstream use with ``dfetch format-patch``
2020

21-
----
22-
2321
.. _patching-create:
2422

2523
Capturing local changes
@@ -57,8 +55,6 @@ base. You can override this:
5755

5856
.. scenario-include:: ../features/diff-in-svn.feature
5957

60-
----
61-
6258
.. _patching-wire:
6359

6460
Adding the patch to the manifest
@@ -81,8 +77,6 @@ From this point on, every ``dfetch update`` will fetch the upstream source and
8177
re-apply the patch on top. See :ref:`patch` in the manifest reference for the
8278
full attribute syntax.
8379

84-
----
85-
8680
.. _patching-update:
8781

8882
Refreshing a patch
@@ -112,8 +106,6 @@ as you iterate on the fix.
112106

113107
.. scenario-include:: ../features/update-patch-in-svn.feature
114108

115-
----
116-
117109
.. _patching-upstream:
118110

119111
Contributing the patch upstream

doc/howto/sbom.rst

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,8 +33,6 @@ supply-chain integrity verification.
3333
.. scenario-include:: ../features/report-sbom-archive.feature
3434
:scenario: A fetched archive with sha256 hash generates a json sbom with hash
3535

36-
----
37-
3836
GitLab
3937
------
4038

@@ -53,8 +51,6 @@ dependency scanning dashboard. See `GitLab dependency scanning`_ for details.
5351
cyclonedx:
5452
- dfetch.cdx.json
5553
56-
----
57-
5854
GitHub Actions
5955
--------------
6056

doc/index.rst

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,6 @@ upstream. See :ref:`vendoring` for background on the problem this solves.
3737

3838
.. asciinema:: asciicasts/basic.cast
3939

40-
----
41-
4240
.. toctree::
4341
:maxdepth: 2
4442
:caption: Tutorials

0 commit comments

Comments
 (0)