Expand the "Handling compatibility breakages" section#58
Open
southpawriter02 wants to merge 7 commits intogodotengine:mainfrom
Open
Expand the "Handling compatibility breakages" section#58southpawriter02 wants to merge 7 commits intogodotengine:mainfrom
southpawriter02 wants to merge 7 commits intogodotengine:mainfrom
Conversation
Ivorforce
reviewed
Feb 9, 2026
Co-authored-by: Lukas Tenbrink <lukas.tenbrink@gmail.com>
…outhpawriter02/godot-contributing-docs into expand-compatibility-breakages
Co-authored-by: Lukas Tenbrink <lukas.tenbrink@gmail.com>
Co-authored-by: A Thousand Ships <96648715+AThousandShips@users.noreply.github.com>
Removed some very confusing high-level definitions.
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
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.
The "Handling compatibility breakages" section in
engine/guidelines/index.rsthad a TODO asking to elaborate on the types of compatibility and procedure. The only other content was a bare link to the external docs page. This meant a contributor landing here got no orientation before being sent elsewhere.This fills in that section with a brief overview:
The external docs link is preserved at the bottom for anyone who needs the full technical walkthrough. The section is meant to orient contributors, not replace the external page, so it stays high-level on purpose.