Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.To avoid long lists and clutter both the screen and logs. It will also improve performance as we do not make less Drupal API calls while processing by just adding project-specific info to an array to be used in the aggregated message as an item list.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | gitinfo-corrections_of_messages-3144338-11.patch | 10.72 KB | lolandese |
| #8 | gitinfo-aggregate_messages-3144338-8.patch | 59.65 KB | lolandese |
| #6 | gitinfo-aggregate_messages-3144338-6.patch | 58.08 KB | lolandese |
| #3 | gitinfo-aggregate_messages-3144338-3.patch | 48.23 KB | lolandese |
Comments
Comment #2
lolandese commentedTo note that with log messages the latest appears on top while with screen messages that is opposite.
Comment #3
lolandese commentedSaving some work. (WIP)
Comment #4
lolandese commentedWIP, not finished.
Comment #5
lolandese commentedBorrowed code from the patch in #1325736: Create a consistent method to link to watchdog log reports to get the link to the latest log message. To compress the screen messages to the max, we just provide a link to the associated log message for details.
Comment #6
lolandese commentedComment #7
lolandese commentedTo restore the links to the instructions (private repos and 'sudo git' for user www-data).
Furthermore, to see if we can identify and group the highlighted issues.
Comment #8
lolandese commentedWe prefer to not extend the screen and log messages to the report items itself but limit it to HEAD fix, fetch, and pull.
Links to instructions are restored and even included in the log messages besides the screen messages.
Comment #10
lolandese commentedComment #11
lolandese commentedAfter many recent changes, the messages were screwed up. The patch fixes that.
Comment #13
lolandese commented