Skip to content

Conversation

forstisabella
Copy link
Contributor

@forstisabella forstisabella commented Mar 21, 2025

Proposed changes

Added docs for the new bidirectional sync feature!

Merge timing

after approval from Atit and Dean

Related issues (optional)

@forstisabella forstisabella requested a review from deanhuynh March 21, 2025 16:22
@forstisabella forstisabella requested a review from a team as a code owner March 21, 2025 16:22
@forstisabella forstisabella requested review from pwseg and stayseesong and removed request for stayseesong March 21, 2025 16:22
Copy link

netlify bot commented Mar 21, 2025

Deploy Preview for segment-docs ready!

Name Link
🔨 Latest commit 4cc6eb1
🔍 Latest deploy log https://app.netlify.com/sites/segment-docs/deploys/67e2b3b7013fa80008e18e2b
😎 Deploy Preview https://deploy-preview-7515--segment-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

pwseg
pwseg previously approved these changes Mar 25, 2025
Copy link
Contributor

@pwseg pwseg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Handful of minor suggestions.

## Bidirectional Sync
Bidirectional sync builds on top of the Git Sync extension and lets you manage your Segment workspace directly in GitHub. After you configure and enable bidirectional sync, Segment automatically listens for pull requests in your repository and manages all related workspace changes. Segment will not apply any changes unless the pull request has met all merge requirements and can be merged.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we tighten that last sentence to something like "Segment only applies changes from pull requests that meet all merge requirements"?

Bidirectional sync does not support variables, references to other resources, or resources from other providers.
> warning "Bidirectional sync can lead to broad workspace changes, including data loss"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screenshot 2025-03-25 at 10 27 59 AM

Should this be rendered differently?

Bidirectional sync builds on top of the Git Sync extension and lets you manage your Segment workspace directly in GitHub. After you configure and enable bidirectional sync, Segment automatically listens for pull requests in your repository and manages all related workspace changes. Segment only applies changes from pull requests that you successfully merge.
Bidirectional sync only supports:
- Explicit values (secrets require additional configuration)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to link to the secrets section here?

## Bidirectional Sync
Bidirectional sync builds on top of the Git Sync extension and lets you manage your Segment workspace directly in GitHub. After you configure and enable bidirectional sync, Segment automatically listens for pull requests in your repository and manages all related workspace changes. Segment only applies changes from pull requests that you successfully merge.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we change the last sentence please? Segment won't apply changes that are merged, only those that the user explicitly accepts by commenting segment apply so might be a little bit misleading? The flow is as follows:

Screenshot 2025-03-25 at 10 34 22 AM

@forstisabella forstisabella requested a review from deanhuynh March 26, 2025 17:20
@forstisabella forstisabella merged commit 7fa61ff into develop Mar 27, 2025
4 checks passed
@forstisabella forstisabella deleted the bidirectional-sync branch March 27, 2025 18:54
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants