Lines Matching refs:it

40    hyperium/tonic [issue tracker][issues] is the way to report it.
76 the issue, it becomes impossible for us to fix.
88 Once an issue has been opened, it is not uncommon for there to be discussion
89 around it. Some contributors may have differing opinions about the issue,
109 and triaging issues, but carries with it a necessary review and approval
119 documentation) are greatly appreciated. Before making a large change, it is
127 example), it is either adding new functionality to a crate or it is fixing
224 any single Pull Request may have, and many contributors find it easier to review
253 4. If your patch fixes an open issue, you can add a reference to it at the end
275 nicely even when it is indented.
320 towards improving the contribution as opposed to simply blocking it. If there
347 4. Is the commit message readable and correct? If it contains a breaking change
348    is it clear enough?
382 If a Pull Request appears to be abandoned or stalled, it is polite to first
384 checking if they would mind if you took it over (especially if it just has nits
385 left). When doing so, it is courteous to give the original contributor credit
404 2. In general, tonic tries to keep all crates at the same version to make it
414    changelog. Tonic uses `conventional-changelog` and it's cli to generate the