Lines Matching refs:changes

69 - For any new features or API changes you introduced add information on them to `doc/changes/dev.rs…
71 - Inspect changes and stage code using standard Git commands, e.g.
118 - Include {doc}`tests </developers/testing>` which cover any changes to the source code.
142 Often a branch's commit history does not present a logical series of changes.
143 … bug-fixes or tiny improvements may accumulate. One commit may contain multiple orthogonal changes.
144 The order of changes may be incorrect. Branches without a clean commit history will often break `gi…
145 …ass the PETSc CI testing, while presenting a small-as-possible set of very closely related changes.
164 … branch is not compatible with the remote copy of the branch. You must force push your changes with
171 otherwise you will lose those changes. Never do a `git pull` immediately after you rebase since tha…
173 You can use `git log` to see the recent changes to your branch and help determine what commits shou…
181 …[^rebase-not-merge-upstream], if the integration branch has had relevant changes since you started…