Add missing documentation about how to combine a series of GitHub commits into one commit #450
Labels
complexity: small
All steps are laid out in detail so that someone new to the project can work on it
feature: docs: PD team documentation
documentation on PD team processes and architecture, etc.
ready for dev lead
role: back end
role: dev
size: 0.25pt
Can be done in 0.5-1.5 hours
Milestone
Overview
We are striving to write documentation that helps developers on our team and our stakeholders' teams work smoothly and successfully.
We need to add information about how to combine a series of GitHub commits, so that the PR process is simplified and migration conflicts are more easily dealt with.
Documentation Notes
What's missing?
This is a quick way of combining a series of GitHub commits into one:
--no-edit
flag if you want to edit the commit message.Although there are other ways of combining GitHub commits (like
lazygit
and the standard interactive rebase), these are more interactive than the process described above and therefore more difficult to describe in text form.Where would this information have been useful?
main
, in order to make it easier to work with.upstream/main
, especially when there are also migration conflicts in which more than one commit in the PR contains migration files. If the PR commits are all merged into one, the migration conflicts can be simplified along with the repetitive need to resolve merges.Which roles will benefit most from this information?
Action Items
/docs/contributing/
sub-folder listed in Resource 1.01 below.Resources/Instructions/Tags
/docs/contributing/
folder or sub-folders/docs/contributing/howto/
/docs/contributing/tutorial/
The text was updated successfully, but these errors were encountered: