Skip to content

Add Segment track calls to code copy button #178

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

Merged
merged 3 commits into from
Dec 19, 2024

Conversation

colegoldsmith
Copy link
Collaborator

Adding Segment track calls to the copy button on code blocks

@mlr

This comment was marked as outdated.

@plpesvc-ds

This comment was marked as outdated.

@mlr
Copy link
Contributor

mlr commented Dec 19, 2024

UI bundle preview build successful! ✅
Deploying preview to GitHub Pages.
Deployment successful! View preview

@plpesvc-ds
Copy link

plpesvc-ds commented Dec 19, 2024

Build successful! ✅
Deploying draft.
Deploy successful! View draft

1 similar comment
@plpesvc-ds
Copy link

plpesvc-ds commented Dec 19, 2024

Build successful! ✅
Deploying draft.
Deploy successful! View draft

@colegoldsmith
Copy link
Collaborator Author

This is a little hard to test because the draft build only builds the home docs repo, which doesn't have any code blocks. Also the draft build stopped working on the second run because it didn't rebuild the docs home pages, which are pointing at an old hash of the site.js file

@colegoldsmith
Copy link
Collaborator Author

Best way to test this I think is going to be with the PR to update the UI bundle version in the datastax-docs-site repo

@eric-schneider eric-schneider changed the title Code snippet analytics Add Segment track calls to code copy button Dec 19, 2024
@eric-schneider eric-schneider merged commit 0e22295 into main Dec 19, 2024
2 checks passed
@eric-schneider eric-schneider deleted the code-snippet-analytics branch December 19, 2024 23:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants