swarm-derive: specify NetworkBehaviour by full path
Description
Specify NetworkBehaviour as ::libp2p::swarm::NetworkBehaviour in derive.
Links to any relevant issues
https://github.com/libp2p/rust-libp2p/issues/2921
Open Questions
Change checklist
- [x] I have performed a self-review of my own code
- [x] I have made corresponding changes to the documentation
- [ ] I have added tests that prove my fix is effective or that my feature works
- [x] A changelog entry has been made in the appropriate crates
@folex can you grant me permissions to merge master into your branch? I have a bunch of pull requests lined up, thus having me do it will safe a bit of time on both ends.
@folex can you grant me permissions to merge
masterinto your branch? I have a bunch of pull requests lined up, thus having me do it will safe a bit of time on both ends.
I don't see how to do that in GitHub without actually adding you to the fluencelabs org -_-
@folex can you grant me permissions to merge
masterinto your branch? I have a bunch of pull requests lined up, thus having me do it will safe a bit of time on both ends.I don't see how to do that in GitHub without actually adding you to the fluencelabs org -_-
There is a checkbox next to the people that are subscribed to the PR that will allow us to push to this branch only.
@folex can you grant me permissions to merge
masterinto your branch? I have a bunch of pull requests lined up, thus having me do it will safe a bit of time on both ends.I don't see how to do that in GitHub without actually adding you to the fluencelabs org -_-
There is a checkbox next to the people that are subscribed to the PR that will allow us to push to this branch only.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork
Seems like that doesn't work with organisations, only with personal forks. 🤔