diff options
| author | Jan Tojnar <jtojnar@gmail.com> | 2021-05-13 12:46:41 +0200 |
|---|---|---|
| committer | Jan Tojnar <jtojnar@gmail.com> | 2021-05-13 13:58:14 +0200 |
| commit | 6225647cfc829df39c46e4d02c28cea1f029b7db (patch) | |
| tree | f95de44434a19d6dd4e86b552c0a2e7c79b616a8 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | d1601a40c48426ae460eede1675fd1d6ee23e198 (diff) | |
.github/workflows/merge-staging.yml: Include branch in comment
If I receive the mail notification that staging(-next) merge failed,
I either need to check `git log staging-next` or click the action run link
to find out where should I resolve the conflict.
To save time, let’s include the information about which step failed right in the comment.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions