chore: Switch PR testing from trunk to 6.5#3902
Merged
michalChrobot merged 1 commit intodevelop-2.0.0from Mar 17, 2026
Merged
Conversation
6 tasks
michalChrobot
approved these changes
Mar 17, 2026
Member
michalChrobot
left a comment
michalChrobot
left a comment
There was a problem hiding this comment.
To be honest I remember I wanted to do similar thing as trunk from time to time is unstable like this but I'm not sure why I didn't do this/where it went
Anyway, I think it's ok to run something lower then trunk on PRs as this will allow our tests to be more stable + we test daily/weekly on trunk anyway so we should be able to catch those issues
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
2 participants
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.
Purpose of this PR
Trunk is currently integrating a lot of new features and so introduces some instabilities into our testing. This PR moves our PR trigger tests from trunk to 6.5.
Jira ticket
n/a
Changelog
Internal changes only
Documentation
Testing & QA (How your changes can be verified during release Playtest)
Functional Testing
Manual testing :
Manual testing doneAutomated tests:
Covered by existing automated testsCovered by new automated testsDoes the change require QA team to:
Review automated tests?Execute manual tests?Provide feedback about the PR?If any boxes above are checked the QA team will be automatically added as a PR reviewer.
Backports
n/a