Repository navigation
Conversation
Development of breaking changes happens on `next/<track>` trunks while `master` stays available for maintenance releases. Run the push and pull request workflows on those trunks like on `master`.
Console SDKs get `next/<track>` branches that adapt to the native development trunks. Resolve the console branch from the native commit under test by comparing it against `master` and every `next/*` head and selecting the trunk it is fewest commits ahead of. This covers pushes, release branches, which craft cuts from their merge target without a PR, and stacked PRs where only the bottom PR targets the trunk. Ties before a track diverges select `main`. Run unit tests on `next/*` pushes like on `master`, and report a failed resolution or dispatch as a failed status instead of leaving the pending status in place.
Create a console `next/<track>` branch from `main` when the resolved branch does not exist yet, so only the native trunk is created by hand.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2194 +/- ##
==========================================
+ Coverage 75.39% 75.58% +0.18%
==========================================
Files 103 103
Lines 28208 28208
Branches 5168 5168
==========================================
+ Hits 21268 21321 +53
+ Misses 5600 5535 -65
- Partials 1340 1352 +12 🚀 New features to boost your workflow:
|
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.
Run CI on
next/*like onmaster, and dispatch console compatibility checks to the console branch matching the PR base branch.This allows developing 1.0 in
next/1.0with the console repositories migrating in parallel in their ownnext/1.0branches, while nativemasterand consolemainbranches stay open for 0.x maintenance releases and remain compatible withsentry-unrealandsentry-unity.