Skip to content

Commit 120dde5

Browse files
committed
fix(logs): update references hyperlinks for git depth logs
close #375
1 parent 91e99a5 commit 120dde5

File tree

1 file changed

+3
-3
lines changed
  • mkdocs_rss_plugin/git_manager

1 file changed

+3
-3
lines changed

mkdocs_rss_plugin/git_manager/ci.py

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ def raise_ci_warnings(self) -> None:
5252
Running on a gitlab runner might lead to wrong \
5353
git revision dates due to a shallow git fetch depth. \
5454
Make sure to set GIT_DEPTH to 1000 in your .gitlab-ci.yml file. \
55-
(see https://docs.gitlab.com/ee/user/project/pipelines/settings.html#git-shallow-clone).
55+
(see https://docs.gitlab.com/user/project/repository/monorepos/#use-shallow-clones-in-cicd-processes).
5656
"""
5757
)
5858

@@ -64,7 +64,7 @@ def raise_ci_warnings(self) -> None:
6464
Running on github actions might lead to wrong \
6565
git revision dates due to a shallow git fetch depth. \
6666
Try setting fetch-depth to 0 in your github action \
67-
(see https://github.com/actions/checkout).
67+
(see https://github.com/actions/checkout?tab=readme-ov-file#fetch-all-history-for-all-tags-and-branches).
6868
"""
6969
)
7070

@@ -76,7 +76,7 @@ def raise_ci_warnings(self) -> None:
7676
Running on bitbucket pipelines might lead to wrong \
7777
git revision dates due to a shallow git fetch depth. \
7878
Try setting "clone: depth" to "full" in your pipeline \
79-
(see https://support.atlassian.com/bitbucket-cloud/docs/configure-bitbucket-pipelinesyml/
79+
(see https://support.atlassian.com/bitbucket-cloud/docs/git-clone-behavior/#Depth
8080
and search 'depth').
8181
"""
8282
)

0 commit comments

Comments
 (0)