diff options
| author | benaryorg <binary@benary.org> | 2024-02-23 17:28:16 +0000 |
|---|---|---|
| committer | benaryorg <binary@benary.org> | 2024-02-23 17:28:16 +0000 |
| commit | c3b66ce3ccefe0bb951c406d5b0b77373512e3d0 (patch) | |
| tree | edc97e007f7959ea0fac2c6c90f4986c8eab648a /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | b093dd8294d77aeb761a6f3c616e9e3dd9578c20 (diff) | |
CONTRIBUTING.md: change table column order for staging
The graph right above the table has the order as `master` ⇒ `staging-next` ⇒ `staging`.
This corresponds with the workflow, i.e. automatic merges happen in that direction and the manual merging is in reverse direction of that.
As a first time reader of this document the table was very confusing due to the disparity of that.
With this change the table should read more fluently for people not familiar with the workflow since the table follows the step-by-step flow of commits.
Signed-off-by: benaryorg <binary@benary.org>
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions