Jan Mikeš
Jan Mikeš
Basically when git history diverges and expects never to merge together again: - Scenario: open source packages with semver - Scenario: proprietary software, which needs to keep BC Feature requested...
Situation: I create task to restart servers every sunday morning, as soon as i save the task, it will get scheduled, because it never run before and will run for...
Use case with baseline: - company has versioned `vendor` directory and do not want it to be processed when they update composer Usecase for both "all codebase" option and "baseline":...
Sometimes it happens (especially for big codebase) that sub-process is killed due to OOM: ``` [ 2374.680372] Out of memory: Killed process 10912 (php) total-vm:3659936kB, anon-rss:3551220kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:7156kB...
As a user, i would like to know, the job succeeded, but changed nothing - it can be confusing to see "success" without merge request. 2 scenarios can happen: -...
It might be useful for experimenting with recipes - when recipe is enabled with baseline, as a user i still want to have possibility to try running it on all...
``` /var/www/worker/var/working_directories/mamlxejqmn/projects/dms/src/Shared/Domain/Date/Date.php on line 8 ``` The `/var/www/worker/var/working_directories/mamlxejqmn` should not leak ANYWHERE - it is implementation detail and user should not be bothered about it.