[OSDOCS-16995]: Adding content types to modules: F-I #101242
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci
bot
added
the
size/XS
|
🤖 Wed Oct 29 16:47:37 - Prow CI generated the docs preview: |
lahinson
force-pushed
the
osdocs-16995-add-content-types-f-i
branch
from
b383ae5 to
84eec1f
Compare
openshift-merge-robot
added
the
needs-rebase
openshift-ci
bot
added
size/S
lahinson
force-pushed
the
osdocs-16995-add-content-types-f-i
branch
from
84eec1f to
593e7ff
Compare
openshift-ci
bot
added
size/M
lahinson
force-pushed
the
osdocs-16995-add-content-types-f-i
branch
from
593e7ff to
ac0c1f8
Compare
openshift-merge-robot
removed
the
needs-rebase
lahinson
force-pushed
the
osdocs-16995-add-content-types-f-i
branch
from
ac0c1f8 to
00b022d
Compare
openshift-ci
bot
added
size/L
lahinson
added
branch/enterprise-4.14
branch/enterprise-4.15
branch/enterprise-4.18
branch/enterprise-4.19
branch/enterprise-4.20
branch/enterprise-4.17
branch/enterprise-4.21
merge-review-needed
ShaunaDiaz
added
merge-review-in-progress
ShaunaDiaz
reviewed
Oct 29, 2025
| // | ||
| // * security/file_integrity_operator/file-integrity-operator-understanding.adoc | ||
|
|
||
| :_mod-docs-content-type: CONCEPT |
Contributor
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 |
Contributor
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 |
Contributor
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 |
Contributor
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.
Contributor
Author
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 |
ShaunaDiaz
added
ok-to-merge
and removed
merge-review-in-progress
lahinson
force-pushed
the
osdocs-16995-add-content-types-f-i
branch
from
00b022d to
46b859c
Compare
|
@lahinson: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
Contributor
Author
|
/cherrypick enterprise-4.21 |
Contributor
Author
|
/cherrypick enterprise-4.20 |
Contributor
Author
|
/cherrypick enterprise-4.19 |
Contributor
Author
|
/cherrypick enterprise-4.18 |
Contributor
Author
|
/cherrypick enterprise-4.17 |
Contributor
Author
|
/cherrypick enterprise-4.16 |
Contributor
Author
|
/cherrypick enterprise-4.15 |
|
@lahinson: new pull request created: #101319 In 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. |
Contributor
Author
|
/cherrypick enterprise-4.14 |
|
@lahinson: new pull request created: #101320 In 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 In 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 In 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 In 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": In 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": In 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": In 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. |
This was referenced Oct 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.