Skip to content

Conversation

@b5
Copy link
Member

@b5 b5 commented Dec 2, 2025

Description

learning how to make proper rust docs contributions, clarifying my understanding of what online does, and adding an example.

Breaking Changes

Notes & open questions

Change checklist

  • Self-review.
  • Documentation updates following the style guide, if relevant.
  • Tests if relevant.
  • All breaking changes documented.
    • List all breaking changes in the above "Breaking Changes" section.
    • Open an issue or PR on any number0 repos that are affected by this breaking change. Give guidance on how the updates should be handled or do the actual updates themselves. The major ones are:

@github-actions
Copy link

github-actions bot commented Dec 2, 2025

Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh/pr/3722/docs/iroh/

Last updated: 2025-12-02T02:32:47Z

@github-actions
Copy link

github-actions bot commented Dec 2, 2025

Netsim report & logs for this PR have been generated and is available at: LOGS
This report will remain available for 3 days.

Last updated for commit: 860bb2f

@n0bot n0bot bot added this to iroh Dec 2, 2025
@github-project-automation github-project-automation bot moved this to 🏗 In progress in iroh Dec 2, 2025
@flub
Copy link
Contributor

flub commented Dec 2, 2025

Could you also take #3713 into account and call out that this doesn't interact with the discovery mechanisms?

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

Labels

None yet

Projects

Status: 🏗 In progress

Development

Successfully merging this pull request may close these issues.

3 participants