Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 7 commits
- 97 files changed
- 2 contributors
Commits on Jun 29, 2024
-
Run e2e tests in parallel (#1990)
* Run e2e tests in parallel * Change function name * Install composer dependencies in parallel * Fix syntax issue * Run composer in parallel for e2e tests * Temp change to fail e2e tests * Revert "Temp change to fail e2e tests" This reverts commit 61f0642. * Simplify initialization of error.log * Initialize infection executable variable in function
-
Commits on Jul 14, 2024
-
-
Un-prophecyze in favor of phpunit mock (#1993)
* Un-prophecyze in favor of phpunit mock * update phpstan
Commits on Jul 15, 2024
Commits on Sep 8, 2024
-
Add PHP 8.4 to the pipeline (#1992)
* Add PHP 8.4 to the pipeline * Update symfony/phpunit-bridge to minimum supported version (5.4) * Install latest 9.6 to avoid deprecations * Use new phpunit config structure
Commits on Oct 6, 2024
-
Fallback to the simple diff colorizer (previous implementation) for m…
…ultiline diffs. (#2000) We introduced inline highlighter for diffs in #1974 (thanks to @Slamdunk). However, there was an incorrect assumption that we only have one-line diffs. This is not true. The case which is currently fails is the following: ```diff @@ @@ */ protected function name() { - return strtolower(get_class($this)); + strtolower(get_class($this)); + return null; } } ``` I check how `diff-so-fancy` works with multiline diffs, and it turned out that it just skips inline diffs, using simple algorithm, see images below. So, for the cases when we have multiline diffs, I just added fallback - our old algorithm of colorizing diffs.
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 0.29.6...0.29.7