Skip to content
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

Bidirectional Sync docs #7515

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from
Open

Bidirectional Sync docs #7515

wants to merge 4 commits into from

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 stayseesong and pwseg 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.

@@ -84,6 +84,45 @@ To manage Segment resources using Git and Terraform, follow these steps:

For more information on using Terraform, visit [Terraform's documentation](https://developer.hashicorp.com/terraform/docs){:target="_blank"}.

## 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"

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?


1. **Navigate to the Git Sync settings page to verify that your Git Sync integration is set up with Segment's GitHub App integration.** If it isn't, you can change the connection type under **Settings > Extensions > Git Sync > Manage Configuration**. If you were previously using the GitHub App integration, you might need to accept additional GitHub permissions that allow Segment to listen for the relevant events.
2. **Add branch protection to your GitHub repository**. You can update your branch protections by opening GitHub and navigating to **Settings > Rules > Rulesets** and adding the Segment Extensions app to the **Bypass list**.
3. **Navigate to the Segment app and enable Git sync bidirectional sync.** From the Segment app, navigate to **Settings > Extentions > Git Sync** page and enabling the **Git sync bidirectional sync** setting.

Choose a reason for hiding this comment

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

Suggested change
3. **Navigate to the Segment app and enable Git sync bidirectional sync.** From the Segment app, navigate to **Settings > Extentions > Git Sync** page and enabling the **Git sync bidirectional sync** setting.
3. **Navigate to the Segment app and enable Git sync bidirectional sync.** From the Segment app, navigate to **Settings > Extentions > Git Sync** page and enable the **Git sync bidirectional sync** setting.

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)

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?

@@ -84,6 +84,45 @@ To manage Segment resources using Git and Terraform, follow these steps:

For more information on using Terraform, visit [Terraform's documentation](https://developer.hashicorp.com/terraform/docs){:target="_blank"}.

## 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.

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

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 Author

Choose a reason for hiding this comment

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

Suggested change
- Explicit values (secrets require additional configuration)
- Explicit values ([secrets](#use-secrets-with-bidirectional-sync) require additional configuration)

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