-
Notifications
You must be signed in to change notification settings - Fork 226
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
proposal: merge all of trunk into release-pismo #6364
Labels
enhancement
New feature or request
Comments
@Tartuffo and @arirubinstein approve the plan |
warner
added a commit
that referenced
this issue
Sep 30, 2022
This is a merge from `release-pismo` into current `master`. The few conflicts were resolved in favor of what was already on `master`. The patch-package diff on `release-pismo` for endo/bundle-source 2.3.0 was removed, because `master` had been upgraded to 2.3.1, and had its own patch. This ensures that we haven't left any changes behind (included in release-pismo but not on trunk). Once complete, we can fast-forward `release-pismo` to this commit, to complete #6364 ("merge all of trunk into release-pismo"). At that point, both branches will have this commit as their shared common ancestor.
Ok, I merged everything from |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
Some of the changes we want to include on
release-pismo
touch many files (typescript improvements), and cherry-picking the minimal set of changes torelease-pismo
is hard work. If we can afford to just include everything currently on trunk inrelease-pismo
, it would be a lot easier.Changes currently on trunk that are not on release-pismo
Since we forked off
release-pismo
, themaster
branch has commits for the following PRs (oldest first):The text was updated successfully, but these errors were encountered: