Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anax v3.1 syncbranches doc #4067

Merged
merged 10 commits into from
Jan 13, 2025
Merged

Anax v3.1 syncbranches doc #4067

merged 10 commits into from
Jan 13, 2025

Conversation

anaxceron
Copy link
Collaborator

Describe your pull request here: Updating docs-staging branch w/ master branch

List the file(s) included in this PR: many.md

After creating the PR, follow the instructions in the comments.

janan07 and others added 6 commits January 6, 2025 17:15
Signed-off-by: Andrew Jandacek <[email protected]>
fix link syntax to include .md file type
Signed-off-by: anaxceron <[email protected]>
Signed-off-by: anaxceron <[email protected]>
@anaxceron anaxceron added area: docs Documentation issue or issues that have documentation impact release: V3 Zowe V3 content labels Jan 13, 2025
@anaxceron anaxceron self-assigned this Jan 13, 2025
Copy link

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these steps.

  • Add the label review: sme if an SME needs to check your content.
  • Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
  • Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
    • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
  • Link any Doc Issues related to this PR.
  • Fix broken links found in your content areas.
  • Notify the SME to review this PR (if applicable).
  • Merge to the master branch if your PR updates content that is on the live site. Merge to docs-staging if your PR updates content for a future release.

1 similar comment
Copy link

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these steps.

  • Add the label review: sme if an SME needs to check your content.
  • Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
  • Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
    • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
  • Link any Doc Issues related to this PR.
  • Fix broken links found in your content areas.
  • Notify the SME to review this PR (if applicable).
  • Merge to the master branch if your PR updates content that is on the live site. Merge to docs-staging if your PR updates content for a future release.

Copy link

github-actions bot commented Jan 13, 2025

@github-actions github-actions bot temporarily deployed to pull request January 13, 2025 21:02 Inactive
@github-actions github-actions bot temporarily deployed to pull request January 13, 2025 21:34 Inactive
@github-actions github-actions bot temporarily deployed to pull request January 13, 2025 22:10 Inactive
@anaxceron anaxceron merged commit 81f8395 into docs-staging Jan 13, 2025
4 checks passed
@anaxceron anaxceron deleted the anax-v3.1-syncbranches-doc branch January 13, 2025 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: docs Documentation issue or issues that have documentation impact release: V3 Zowe V3 content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants