diff options
| author | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-12-01 16:42:50 +0000 |
|---|---|---|
| committer | Mohammad Akhlaghi <mohammad@akhlaghi.org> | 2020-12-01 16:47:31 +0000 |
| commit | e796e6f401d6d7249aa6165e62354bcada3f732a (patch) | |
| tree | a8db243f6622e513ec5dcc0d08f7b90f1fd938aa /reproduce/software/patches | |
| parent | ac8eee90b1580fb566ee5b84fef9acb4ed437c01 (diff) | |
README-hacking.md: recommended to push maneage after merging
Until now at the end of the updating process, we hadn't explicity talked
about pushing the branches. So people would usually only push their
'master' branch to their remote. While the merged 'master' branch does
contain the commits from the core Maneage branch, having a no-updated
'maneage' branch reference on their remote can be confusing.
With this commit, at the end of the process to merge with the 'maneage'
branch we explicitly recommend to push both the 'master' and 'maneage'
branches.
Diffstat (limited to 'reproduce/software/patches')
0 files changed, 0 insertions, 0 deletions