Skip to content

Test tag#919

Closed
kprosise wants to merge 13 commits intofoundriesio:mainfrom
kprosise:test-tag
Closed

Test tag#919
kprosise wants to merge 13 commits intofoundriesio:mainfrom
kprosise:test-tag

Conversation

@kprosise
Copy link
Copy Markdown
Contributor

PR Template and Checklist

Please complete as much as possible to speed up the reviewing process.
You may delete items that are not relevant to your contribution.
Readiness and adding reviewers as appropriate is required.

All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.

Readiness

  • Merge (pending reviews)
  • Merge after date or event
  • Draft

Checklist

  • Run spelling and grammar check, preferably with linter.
  • Step through instructions (or ask someone to do so).
  • Review for wordiness
  • Match tone and style of page/section.
  • Run make linkcheck, and add redirects for any moved or deleted pages.
  • View HTML in a browser to check rendering.
  • Use semantic newlines.
  • follow best practices for commits.
    • Descriptive title written in the imperative.
    • Include brief overview of QA steps taken.
    • Mention any related issues numbers.
    • End message with sign off/DCO line (-s, --signoff).
    • Sign commit with your gpg key (-S, --gpg-sign).
    • Squash commits if needed.
  • Request PR review by a technical writer and at least one peer.

Comments

Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

kprosise added 13 commits April 1, 2026 08:32
Note that the link is non-functional. This is just a simple step towards
having a dev version, and testing out using the `next` branch for this.

No QA steps taken.

This commit applies to FFTK-4532, "add dev version"

Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
Note that this is a draft/first-go at publishing both a dev version of
the docs, and publishing via a GitHub workflow. This will likely require
additional work. Workflow was kept simple and set to handle a single
case—publish when a commit is merged to dev branch of the docs.

QA steps: Ran `actionlint` on the workflow file, which produced a couple
warnings: possible globbing issue due to expression used for getting the
fioctl version, and a possible side effect for one of the assignments.

This commit applies to issue FFTK-4532, "Add dev version"
This commit applies to issue FFTK-4116, "…GitHub action for publishing"

Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
adding sudo to apt command to address point of failure
Small cleanup to conf.py made in addition to adding the publish-dev
workflow to the workflow path, so as to trigger the workflow when
changes are made to it.

No QA steps preformed.

Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
Removed local-dev, as it isn't really used much.
A fix for published docs to show the dev version will
require (re)publishing to latest.

QA: built locally, no issues found.
No related task/issue, just a small fix/update.

Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
Using dev to test publishing when a tag is added. The new file will
eventually be used for publishing the stable docs, but may be
publishing to dev while potential issues are worked out.

Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
@kprosise kprosise closed this Apr 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant