Revise SKILL.md for updated documentation process#1399
Conversation
Updated the skill documentation to reflect changes in input sources and workflow phases. Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
fix formatting |
christopher-hakkaart
left a comment
christopher-hakkaart
left a comment
There was a problem hiding this comment.
Looks good. I'd be tempted to make the scope narrower (specifically call out master branch and make it the docs repo unless otherwise specified. Just to keep things simple and clear, the more options, the more chance things could go wrong.
|
|
||
| Also read `references/docusaurus-conventions.md` in this skill's directory for Seqera-specific formatting patterns (admonitions, link references, frontmatter, heading hierarchy). | ||
|
|
||
| **Confirm the PR target repo before doing anything else.** Ask the user which repo the eventual PR should target. Default to `seqeralabs/docs`, but offer alternatives like `seqeralabs/platform-enterprise_docs`, a fork, or a feature-specific repo. Hold onto the answer — you'll need it in Phase 6. Also confirm the base branch (default: `master` or `main`, whichever the repo uses). |
There was a problem hiding this comment.
Should this just be seqeralabs/docs with the option of a manual input custom repo?
IMO, it seems like an unnecessary step to list other options when they will be low-usage.
There was a problem hiding this comment.
Do feel free to ignore, comment only
There was a problem hiding this comment.
Agree. This is too general, especially since we don't have a seqeralabs-platform-enterprise_docs repo. It's a folder in the repo.
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
Signed-off-by: Justine Geffen <justinegeffen@users.noreply.github.com>
2 participants
Updated the skill documentation to reflect changes in input sources and workflow phases.