Manually fix broken links (#3331)

docs/source/devguide/styleguide.rst

@@ -55,7 +55,7 @@ Source Files
 Use a ``.cpp`` suffix for code files and ``.h`` for header files.
 
 Header files should always use include guards with the following style (See
-`SF.8 <http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#sf8-use-include-guards-for-all-h-files>`_):
+`SF.8 <https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#Rs-guards>`_):
 
 .. code-block:: C++
 

docs/source/devguide/tests.rst

@@ -87,9 +87,9 @@ that, consider the following:
 Debugging Tests in CI
 ---------------------
 
-.. _tmate: <https://github.com/mxschmitt/action-tmate?tab=readme-ov-file#debug-your-github-actions-by-using-tmate>`_
-
-Tests can be debugged in CI using a feature called `tmate`_. CI debugging can be
+Tests can be debugged in CI using a feature called 
+`tmate <https://github.com/mxschmitt/action-tmate?tab=readme-ov-file#debug-your-github-actions-by-using-tmate>`_. 
+CI debugging can be
 enabled by including "[gha-debug]" in the commit message. When the test fails, a
 link similar to the one shown below will be provided in the GitHub Actions
 output after failure occurs. Logging into the provided link will allow you to

docs/source/devguide/workflow.rst

@@ -126,7 +126,7 @@ reinstalling it). While the same effect can be achieved using the
 :envvar:`PYTHONPATH` environment variable, this is generally discouraged as it
 can interfere with virtual environments.
 
-.. _git: http://git-scm.com/
+.. _git: https://git-scm.com/
 .. _GitHub: https://github.com/
 .. _git flow: https://nvie.com/git-model
 .. _valgrind: https://www.valgrind.org/