Skip to content

fix: track closest peers separately from main routing table #509

fix: track closest peers separately from main routing table

fix: track closest peers separately from main routing table #509

Workflow file for this run

name: Automerge
on: [ pull_request ]
jobs:
automerge:
uses: protocol/.github/.github/workflows/automerge.yml@master
with:
job: 'automerge'