Skip to content

Commit 722e05f

Browse files
mariolenzbardielle
authored andcommitted
Provide links for docsite
1 parent 67dd5d1 commit 722e05f

File tree

1 file changed

+2
-22
lines changed

1 file changed

+2
-22
lines changed

docs/docsite/links.yml

+2-22
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,11 @@
11
---
2-
# This will make sure that plugin and module documentation gets Edit on GitHub links
3-
# that allow users to directly create a PR for this plugin or module in GitHub's UI.
4-
# Remove this section if the collection repository is not on GitHub, or if you do not want this
5-
# functionality for your collection.
62
edit_on_github:
7-
repository: ansible-collections/community.REPO_NAME
3+
repository: ansible-collections/vmware.vmware
84
branch: main
9-
# If your collection root (the directory containing galaxy.yml) does not coincide with your
10-
# repository's root, you have to specify the path to the collection root here. For example,
11-
# if the collection root is in a subdirectory ansible_collections/community/REPO_NAME
12-
# in your repository, you have to set path_prefix to 'ansible_collections/community/REPO_NAME'.
13-
path_prefix: ''
14-
15-
# Here you can add arbitrary extra links. Please keep the number of links down to a
16-
# minimum! Also please keep the description short, since this will be the text put on
17-
# a button.
18-
#
19-
# Also note that some links are automatically added from information in galaxy.yml.
20-
# The following are automatically added:
21-
# 1. A link to the issue tracker (if `issues` is specified);
22-
# 2. A link to the homepage (if `homepage` is specified and does not equal the
23-
# `documentation` or `repository` link);
24-
# 3. A link to the collection's repository (if `repository` is specified).
255

266
extra_links:
277
- description: Report an issue
28-
url: https://github.com/ansible-collections/community.REPO_NAME/issues/new/choose
8+
url: https://github.com/ansible-collections/vmware.vmware/issues/new/choose
299

3010
# Specify communication channels for your collection. We suggest to not specify more
3111
# than one place for communication per communication tool to avoid confusion.

0 commit comments

Comments
 (0)