Merge main into publish to sync branches - #24
Merged
Conversation
The operation step events emitted by startOperation / succeedOperation / failOperation are not yet surfaced anywhere in the product UI, and the renderer-side flag mentioned in this section does not exist in @flashcatcloud/browser-rum. Remove the README section and API reference entries until the feature works end-to-end. The exported functions themselves are unchanged.
…oring docs: remove Operation Monitoring from README
README conflicts resolved by keeping the publish version: the only change main carried was the Operation Monitoring removal, which publish already applied in its own rebranded README.
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.
Summary
main(upstream v0.3.0 + docs: remove Operation Monitoring from README #22) intopublishso the branches share a common ancestor going forward.maincarried was the Operation Monitoring README removal (docs: remove Operation Monitoring from README #22), whichpublishalready applied to its own rebranded README in docs: remove Operation Monitoring from README (publish) #23. README conflicts were resolved by keeping thepublishversion;git diffagainstpublishbefore this merge is empty.Verification
git diff origin/publish <merge-commit>is empty — no file content changes onpublish.