Skip to content

Conversation

zees-dev
Copy link
Contributor

Description

This pull request adds a step to the CI workflow to link the forc-mcp documentation into the Cargo target directory. This ensures that the documentation is available in the correct location during the build process.

Documentation integration:

  • Added a CI job step in .github/workflows/ci.yml to create a symbolic link for the forc-mcp documentation from docs/book/src/forc/plugins/forc_mcp/forc_call_tool to target/docs/book/src/forc/plugins/forc_mcp/forc_call_tool.

Checklist

  • I have linked to any relevant issues.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have updated the documentation where relevant (API docs, the reference, and the Sway book).
  • I have added tests that prove my fix is effective or that my feature works.
  • I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
  • I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
  • I have requested a review from the relevant team or maintainers.

@JoshuaBatty JoshuaBatty requested review from a team September 23, 2025 08:58
@IGI-111 IGI-111 merged commit 637db5d into master Sep 23, 2025
43 checks passed
@IGI-111 IGI-111 deleted the fix/ci-publish-forc-mcp branch September 23, 2025 10:48
Elaela22soL pushed a commit to Elaela22soL/sway that referenced this pull request Sep 26, 2025
## Description
This pull request adds a step to the CI workflow to link the `forc-mcp`
documentation into the Cargo target directory. This ensures that the
documentation is available in the correct location during the build
process.

Documentation integration:

* Added a CI job step in `.github/workflows/ci.yml` to create a symbolic
link for the `forc-mcp` documentation from
`docs/book/src/forc/plugins/forc_mcp/forc_call_tool` to
`target/docs/book/src/forc/plugins/forc_mcp/forc_call_tool`.

## Checklist

- [ ] I have linked to any relevant issues.
- [ ] I have commented my code, particularly in hard-to-understand
areas.
- [ ] I have updated the documentation where relevant (API docs, the
reference, and the Sway book).
- [ ] If my change requires substantial documentation changes, I have
[requested support from the DevRel
team](https://github.com/FuelLabs/devrel-requests/issues/new/choose)
- [ ] I have added tests that prove my fix is effective or that my
feature works.
- [ ] I have added (or requested a maintainer to add) the necessary
`Breaking*` or `New Feature` labels where relevant.
- [ ] I have done my best to ensure that my PR adheres to [the Fuel Labs
Code Review
Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md).
- [ ] I have requested a review from the relevant team or maintainers.

Co-authored-by: z <zees-dev@users.noreply.github.com>
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.

3 participants