Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge 2.20.x into 3.3.x #11679

Merged
merged 10 commits into from
Oct 14, 2024
Merged

Merge 2.20.x into 3.3.x #11679

merged 10 commits into from
Oct 14, 2024

Conversation

derrabus
Copy link
Member

No description provided.

greg0ire and others added 7 commits October 12, 2024 15:46
I think it would be great to use literalinclude for big code snippets,
because our IDEs could warn us about issues, and it would be easily to
showcase our coding standard. Before we do that though, let us validate
that it renders as expected. I have picked a complex example where we
have a configuration block.
README.md Outdated Show resolved Hide resolved
* 2.20.x:
  Bump doctrine/.github from 5.1.0 to 5.2.0 (doctrine#11680)
  Psalm 5.26.1 (doctrine#11677)
  Update README (doctrine#11673)
  Fix PHPUnit deprecations
  Bump doctrine/.github from 5.1.0 to 5.2.0 (doctrine#11671)
  Experiment with literalinclude
@derrabus derrabus merged commit d5c400e into doctrine:3.3.x Oct 14, 2024
85 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants