docs: update gitlab links to include /-/ component

.github/issue_template.md

@@ -1,2 +1,2 @@
 Thanks for trying to contribute to VTK-m.  The GitHub repository is a mirror provided
-for convenience, as VTK-m uses https://gitlab.kitware.com/vtk/vtk-m/issues for issue tracking. 
+for convenience, as VTK-m uses https://gitlab.kitware.com/vtk/vtk-m/-/issues for issue tracking. 

.github/pull_request_template.md

@@ -2,4 +2,4 @@ Thanks for trying to contribute to VTK-m.  The GitHub repository
 is a mirror provided for convenience, as VTK-m uses gitlab.kitware.com
 for all pull requests. Our contribution instructions are located at:
 
-  https://gitlab.kitware.com/vtk/vtk-m/tree/master/CONTRIBUTING.md
+  https://gitlab.kitware.com/vtk/vtk-m/-/tree/master/CONTRIBUTING.md

.gitlab-ci.yml

@@ -95,7 +95,7 @@
 #
 # Current Tasks:
 # - Determine if we can get sccache to work with CUDA
-# - Setup a machine to replicate the issue in https://gitlab.kitware.com/vtk/vtk-m/issues/447
+# - Setup a machine to replicate the issue in https://gitlab.kitware.com/vtk/vtk-m/-/issues/447
 #   Note: Centos7 doesn't work as they ship separate standard library
 #   headers for each version. We will have to figure out something else
 #   like using spack or building llvm/clang from source

CONTRIBUTING.md

@@ -44,7 +44,7 @@ Before you begin, perform initial setup:
     developers and users.
 
 [GitLab Access]: https://gitlab.kitware.com/users/sign_in
-[Fork VTK-m]: https://gitlab.kitware.com/vtk/vtk-m/forks/new
+[Fork VTK-m]: https://gitlab.kitware.com/vtk/vtk-m/-/forks/new
 [Register with the VTK-m dashboard]: https://open.cdash.org/register.php
 [Sign up for the VTK-m mailing list]: http://vtk.org/mailman/listinfo/vtkm
 
@@ -178,7 +178,7 @@ upper right.
 When you [pushed your topic branch](#share-a-topic), it will provide you
 with a url of the form
 
-    https://gitlab.kitware.com/<username>/vtk-m/merge_requests/new
+    https://gitlab.kitware.com/<username>/vtk-m/-/merge_requests/new
 
 You can copy/paste that into your web browser to create a new merge
 request. Alternately, you can visit your fork in GitLab, browse to the

README.md

@@ -230,7 +230,7 @@ See [LICENSE.txt](LICENSE.txt) for details.
 [VTK-m Doxygen]:            http://m.vtk.org/documentation/
 [VTK-m download page]:      http://m.vtk.org/index.php/VTK-m_Releases
 [VTK-m git repository]:     https://gitlab.kitware.com/vtk/vtk-m/
-[VTK-m Issue Tracker]:      https://gitlab.kitware.com/vtk/vtk-m/issues
+[VTK-m Issue Tracker]:      https://gitlab.kitware.com/vtk/vtk-m/-/issues
 [VTK-m Overview]:           http://m.vtk.org/images/2/29/VTKmVis2016.pptx
 [VTK-m Users Guide]:        http://m.vtk.org/images/c/c8/VTKmUsersGuide.pdf
 [VTK-m users email list]:   http://vtk.org/mailman/listinfo/vtkm

docs/ReleaseProcess.md

@@ -179,7 +179,7 @@ contributed to VTK-m since our last release. The 1.5.0 release contains
 over 100000 merge requests, and 100000 entries to the changelog .
 
 Below are all the entries in the changelog, with more details at (
-https://gitlab.kitware.com/vtk/vtk-m/tags/vX.Y.0 ) or in the vtkm
+https://gitlab.kitware.com/vtk/vtk-m/-/tags/vX.Y.0 ) or in the vtkm
 repository at `docs/X.Y/release-notes.md`
 
 1. Core

docs/changelog/1.3/release-notes.md

@@ -75,7 +75,7 @@ new adapter is enabled using the CMake option `VTKm_ENABLE_OPENMP` and its
 performance is comparable to the TBB device adapter.
 
 Performance comparisions of `OpenMP` against the `TBB` and  `Serial` device
-adapters can be found at: https://gitlab.kitware.com/vtk/vtk-m/issues/223
+adapters can be found at: https://gitlab.kitware.com/vtk/vtk-m/-/issues/223
 
 
 ## Make all worklets dispatches invoke using a `TryExecute`

vtkm/Types.h

@@ -688,7 +688,7 @@ public:
   VTKM_EXEC_CONT explicit VecBase(const VecBase<OtherValueType, Size, OtherDerivedType>& src)
   {
     //DO NOT CHANGE THIS AND THE ABOVE PRAGMA'S UNLESS YOU FULLY UNDERSTAND THE
-    //ISSUE https://gitlab.kitware.com/vtk/vtk-m/issues/221
+    //ISSUE https://gitlab.kitware.com/vtk/vtk-m/-/issues/221
     for (vtkm::IdComponent i = 0; i < Size; ++i)
     {
       this->Components[i] = src[i];

vtkm/cont/Logging.h

@@ -203,7 +203,7 @@
 /// \note This macro is to be used for quickly setting log levels.  For a
 /// more maintainable solution it is recommended to create a custom enum class
 /// and then cast appropriately, as described here:
-/// https://gitlab.kitware.com/vtk/vtk-m/issues/358#note_550157
+/// https://gitlab.kitware.com/vtk/vtk-m/-/issues/358#note_550157
 
 #if defined(VTKM_ENABLE_LOGGING)