Skip to content

Conversation

@nluaces
Copy link
Member

@nluaces nluaces commented Aug 28, 2025

No description provided.

@nluaces nluaces requested review from ajssmith and pwright August 28, 2025 18:17
@nluaces nluaces self-assigned this Aug 28, 2025
@nluaces nluaces added the documentation Improvements or additions to documentation label Aug 28, 2025
Copy link
Member

@pwright pwright left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, but what's the intention? run and commit each cli change?
run at release time?

would it make more sense to run and commit into skupper-docs? (and use versioning there for each minor release)

@nluaces
Copy link
Member Author

nluaces commented Sep 1, 2025

what's the intention? run and commit each cli change?

Yes, that's the idea, to have this CLI documentation available in the main repository.

would it make more sense to run and commit into skupper-docs? (and use versioning there for each minor release)

I think this is also a very good idea that we could implement additionally.

@fgiorgetti
Copy link
Member

@nluaces @pwright I like the idea of having this being generated automatically, maybe on each PR merged or as a
scheduled workflow in the CI. Can we get these markdown files incorporated into the skupper-docs somehow?

@nluaces
Copy link
Member Author

nluaces commented Sep 2, 2025

Can we get these markdown files incorporated into the skupper-docs somehow?

should we add the changes per release only in the skupper-docs, like @pwright suggested?

@pwright
Copy link
Member

pwright commented Sep 2, 2025

I would probably add them directly to skupper-website repo, based on release tag

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants