[OSDOCS-16995]: Adding content types to modules: F-I#101242
[OSDOCS-16995]: Adding content types to modules: F-I#101242lahinson merged 1 commit intoopenshift:mainfrom
Conversation
|
🤖 Wed Oct 29 16:47:37 - Prow CI generated the docs preview: |
b383ae5 to
84eec1f
Compare
84eec1f to
593e7ff
Compare
593e7ff to
ac0c1f8
Compare
ac0c1f8 to
00b022d
Compare
| // | ||
| // * security/file_integrity_operator/file-integrity-operator-understanding.adoc | ||
|
|
||
| :_mod-docs-content-type: CONCEPT |
There was a problem hiding this comment.
FWIW this looks like reference to me.
| // | ||
| // * security/file_integrity_operator/file-integrity-operator-understanding.adoc | ||
|
|
||
| :_mod-docs-content-type: CONCEPT |
There was a problem hiding this comment.
I would probably call this Reference as well.
| // | ||
| // * security/file_integrity_operator/file-integrity-operator-understanding.adoc | ||
|
|
||
| :_mod-docs-content-type: CONCEPT |
There was a problem hiding this comment.
I would probably call this Reference as well.
| // | ||
| // * security/file_integrity_operator/file-integrity-operator-configuring.adoc | ||
|
|
||
| :_mod-docs-content-type: CONCEPT |
There was a problem hiding this comment.
According to https://github.com/redhat-documentation/modular-docs/blob/main/modular-docs-manual/files/TEMPLATE_CONCEPT_concept-explanation.adoc, there are not supposed to be gerunds in concept modules. Don't know if this is a DITA problem. Likely beyond the scope of this PR.
There was a problem hiding this comment.
You are right --there are not supposed to be gerunds in concept modules. You are also right that changing the title is beyond the scope of this PR.
| // | ||
| // * installing/installing_azure_stack_hub/installing-azure-stack-hub-user-infra.adoc | ||
|
|
||
| :_mod-docs-content-type: CONCEPT |
00b022d to
46b859c
Compare
|
@lahinson: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/cherrypick enterprise-4.21 |
|
/cherrypick enterprise-4.20 |
|
/cherrypick enterprise-4.19 |
|
/cherrypick enterprise-4.18 |
|
/cherrypick enterprise-4.17 |
|
/cherrypick enterprise-4.16 |
|
/cherrypick enterprise-4.15 |
|
@lahinson: new pull request created: #101319 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/cherrypick enterprise-4.14 |
|
@lahinson: new pull request created: #101320 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@lahinson: new pull request created: #101321 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@lahinson: new pull request created: #101322 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@lahinson: new pull request created: #101323 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@lahinson: #101242 failed to apply on top of branch "enterprise-4.16": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@lahinson: #101242 failed to apply on top of branch "enterprise-4.15": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@lahinson: #101242 failed to apply on top of branch "enterprise-4.14": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Version(s): 4.14+
Issue: https://issues.redhat.com/browse/OSDOCS-16695
Link to docs preview:
QE review:
N/A for this PR
Additional information: This PR is part of the tiger team work to prepare content for migration to DITA.