[Auto] [Update] No documentation changes needed for Events Sheet visual glitch fixes#668
Open
github-actions[bot] wants to merge 1 commit into
Open
[Auto] [Update] No documentation changes needed for Events Sheet visual glitch fixes#668github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was automatically generated by the Update docs from GDevelop commits workflow.
An AI coding agent analysed recent commits in 4ian/GDevelop
and updated the documentation to reflect user-facing changes.
GDevelop commits covered
The AI agent summary is:
No documentation changes were needed. The commit only fixes internal visual glitches in the Events Sheet (virtualized list rendering, scroll-to-row behavior, undo/redo selection handling) — all non-user-facing implementation details that the writing-style guide says shouldn't be documented.
Please review the changes carefully before merging.