ENG-4673 fix(portal): drop graphql related prs on main #895
Conversation
This file contains 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
…proach-for-the-graphql-work-so
|
This looks good to me but still marking with |
jonathanprozzi
approved these changes
Nov 7, 2024
There was a problem hiding this comment.
See other comment -- added do not merge until we align, but this looks good. Thanks for doing this @Vitalsine85
We should hopefully be able to open PRs again onto the feature branch but we should sync about that as a squad.
…proach-for-the-graphql-work-so
|
Marking this ready to merge so that we can cut a release |
jonathanprozzi
changed the title
jonathanprozzi
deleted the
vital/eng-4670-switch-to-a-feature-branch-approach-for-the-graphql-work-so
branch
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.
Affected Packages
Apps
Packages
Tools
Overview
Reverts ENG-4659, 4656, and 4662 in favor of moving all GraphQL related work in Portal to a feature branch. This will allow us to maintain and push releases of Portal without being tied down by the migration.
Screen Captures
If applicable, add screenshots or screen captures of your changes.
Declaration