Lines Matching refs:changes

49    often, by opening a Pull Request that changes some bit of something in
110 workflow that ensures that the proposed changes meet the minimal quality and
115 Pull Requests are the way concrete changes are made to the code, documentation,
211 When making changes to `tonic-build` that affects the generated code you will
222 It is a recommended best practice to keep your changes as logically grouped as
225 changes that are split across multiple commits.
291 You will probably get feedback or requests for changes to your Pull Request.
295 in order to evaluate whether the changes are correct and necessary.
354 When changes are necessary, *request* them, do not *demand* them, and **do not
360 Nits (requests for small changes that are not essential) are fine, but try to
402    changes make sure to select a semver compatible version bump.
423    must also add any breaking changes here as sometimes they get lost.
429    command will release those changes.