sig_core/wiki
7
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Activity

extend explanation of force push

Browse Source
This commit is contained in:
Louis Abel 2022-10-29 16:58:40 -07:00
parent 48a3594170
commit 5e92b70b43
Signed by: label
GPG Key ID: B37E62D143879B36
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/sop/sop_upstream_prep_checklist.md
View File

@ -75,4 +75,6 @@ downward to the stable branch. For example:
This applies to any specific rocky repo, such as comps, pungi, peridot-config, This applies to any specific rocky repo, such as comps, pungi, peridot-config,
and so on. As it is expected some repos will deviate in commit history, it is OK and so on. As it is expected some repos will deviate in commit history, it is OK
to force push. to force push, under the assumption that changes made in the lower branch exists
in the upper branch. That way you can avoid changes/functionality being reverted
on accident.