Add platform code for setting writekey #4050
Merged
Conversation
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
added 2 commits
January 13, 2023 11:04
markzegarelli
suggested changes
Jan 13, 2023
src/connections/sources/catalog/libraries/mobile/react-native/index.md
Outdated
Show resolved
Hide resolved
src/connections/sources/catalog/libraries/mobile/react-native/index.md
Outdated
Show resolved
Hide resolved
…index.md Co-authored-by: markzegarelli <[email protected]>
…index.md Co-authored-by: markzegarelli <[email protected]>
markzegarelli
approved these changes
Jan 17, 2023
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
markzegarelli
pushed a commit
that referenced
this pull request
Jan 17, 2023
* Update faq.md * Developer Center 2.0 documentation (#4007) * Init * Intro edits * Draft complete * Apply suggestions from code review Co-authored-by: forstisabella <[email protected]> * Remove * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Clarifications from Sharan * No longer in Dev preview Co-authored-by: forstisabella <[email protected]> * Update Amplitude Classic Destination DOC-629 * Update EU Endpoint Language DOC-629 * Update index.md Add note about the API Key being region specific * Revert commit * Add section highlighting User Data parameter mappings to Facebook Conversions API Destination (#4025) * Update index.md * Update src/connections/destinations/catalog/actions-facebook-conversions-api/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: markzegarelli <[email protected]> * added react native quick link * add section for api token security * update copy * Small edits * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * Update vale rules (#4055) * posthog: update instructions for Cloud EU * Add Audiences and Journeys Guide [netlify-build] * add correct actions slug (#4060) Co-authored-by: Niall Brennan <[email protected]> * Add platform code for setting writekey (#4050) * add platform code * add platform code * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: markzegarelli <[email protected]> * add info about how data comes from Clearbit (#4040) * add info about how data comes from Clearbit Customers in the past have been confused about dataflow with Clearbit and about why they see analytics-ruby events in their Debugger. This update clarifies that a bit. There are past Zendesk tickets that all confirm Clearbit data comes back to Segment using analytics-ruby. In addition, Clearbit published this line about it in one of their blog posts: https://clearbit.com/blog/enterprise-grade-analytics-for-startups-2#:~:text=Segment%E2%80%99s%20robust%20API%20and%20Ruby%20library%20enabled%20our%20engineering%20team%20to%20quickly%20build%20an%20event%20emitting%20service%20that%20sends%20usage%20and%20behavioral%20data%20from%20Clearbit%20applications%20and%20services%20into%20Segment%2C%20tracking%20everything%20from%20API%20usage%20and%20page%20views%20to%20signups%20and%20subscribe%20events.. * Update src/connections/destinations/catalog/clearbit-reveal/index.md Co-authored-by: markzegarelli <[email protected]> * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * catalog update (#4064) Co-authored-by: Ashton Huxtable <[email protected]> Co-authored-by: forstisabella <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: Sarah Rudy <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: bobbyatsegment <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Xavier Vello <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Spencer Attick <[email protected]>
markzegarelli
pushed a commit
that referenced
this pull request
Jan 18, 2023
* Update faq.md * Developer Center 2.0 documentation (#4007) * Init * Intro edits * Draft complete * Apply suggestions from code review Co-authored-by: forstisabella <[email protected]> * Remove * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Clarifications from Sharan * No longer in Dev preview Co-authored-by: forstisabella <[email protected]> * Update Amplitude Classic Destination DOC-629 * Update EU Endpoint Language DOC-629 * Update index.md Add note about the API Key being region specific * Revert commit * Add section highlighting User Data parameter mappings to Facebook Conversions API Destination (#4025) * Update index.md * Update src/connections/destinations/catalog/actions-facebook-conversions-api/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: markzegarelli <[email protected]> * added react native quick link * add section for api token security * update copy * Small edits * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * Update vale rules (#4055) * posthog: update instructions for Cloud EU * Add Audiences and Journeys Guide [netlify-build] * add correct actions slug (#4060) Co-authored-by: Niall Brennan <[email protected]> * Add platform code for setting writekey (#4050) * add platform code * add platform code * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: markzegarelli <[email protected]> * add info about how data comes from Clearbit (#4040) * add info about how data comes from Clearbit Customers in the past have been confused about dataflow with Clearbit and about why they see analytics-ruby events in their Debugger. This update clarifies that a bit. There are past Zendesk tickets that all confirm Clearbit data comes back to Segment using analytics-ruby. In addition, Clearbit published this line about it in one of their blog posts: https://clearbit.com/blog/enterprise-grade-analytics-for-startups-2#:~:text=Segment%E2%80%99s%20robust%20API%20and%20Ruby%20library%20enabled%20our%20engineering%20team%20to%20quickly%20build%20an%20event%20emitting%20service%20that%20sends%20usage%20and%20behavioral%20data%20from%20Clearbit%20applications%20and%20services%20into%20Segment%2C%20tracking%20everything%20from%20API%20usage%20and%20page%20views%20to%20signups%20and%20subscribe%20events.. * Update src/connections/destinations/catalog/clearbit-reveal/index.md Co-authored-by: markzegarelli <[email protected]> * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * catalog update (#4064) * Add new product limits for Engage (#3965) Co-authored-by: Ashton Huxtable <[email protected]> Co-authored-by: forstisabella <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: Sarah Rudy <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: bobbyatsegment <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Xavier Vello <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Spencer Attick <[email protected]>
markzegarelli
pushed a commit
that referenced
this pull request
Jan 19, 2023
* Release 23.3.2 (#4071) * Update faq.md * Developer Center 2.0 documentation (#4007) * Init * Intro edits * Draft complete * Apply suggestions from code review Co-authored-by: forstisabella <[email protected]> * Remove * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Clarifications from Sharan * No longer in Dev preview Co-authored-by: forstisabella <[email protected]> * Update Amplitude Classic Destination DOC-629 * Update EU Endpoint Language DOC-629 * Update index.md Add note about the API Key being region specific * Revert commit * Add section highlighting User Data parameter mappings to Facebook Conversions API Destination (#4025) * Update index.md * Update src/connections/destinations/catalog/actions-facebook-conversions-api/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: markzegarelli <[email protected]> * added react native quick link * add section for api token security * update copy * Small edits * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * Update vale rules (#4055) * posthog: update instructions for Cloud EU * Add Audiences and Journeys Guide [netlify-build] * add correct actions slug (#4060) Co-authored-by: Niall Brennan <[email protected]> * Add platform code for setting writekey (#4050) * add platform code * add platform code * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: markzegarelli <[email protected]> * add info about how data comes from Clearbit (#4040) * add info about how data comes from Clearbit Customers in the past have been confused about dataflow with Clearbit and about why they see analytics-ruby events in their Debugger. This update clarifies that a bit. There are past Zendesk tickets that all confirm Clearbit data comes back to Segment using analytics-ruby. In addition, Clearbit published this line about it in one of their blog posts: https://clearbit.com/blog/enterprise-grade-analytics-for-startups-2#:~:text=Segment%E2%80%99s%20robust%20API%20and%20Ruby%20library%20enabled%20our%20engineering%20team%20to%20quickly%20build%20an%20event%20emitting%20service%20that%20sends%20usage%20and%20behavioral%20data%20from%20Clearbit%20applications%20and%20services%20into%20Segment%2C%20tracking%20everything%20from%20API%20usage%20and%20page%20views%20to%20signups%20and%20subscribe%20events.. * Update src/connections/destinations/catalog/clearbit-reveal/index.md Co-authored-by: markzegarelli <[email protected]> * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * catalog update (#4064) * Add new product limits for Engage (#3965) Co-authored-by: Ashton Huxtable <[email protected]> Co-authored-by: forstisabella <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: Sarah Rudy <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: bobbyatsegment <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Xavier Vello <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Spencer Attick <[email protected]> * Catalog update for Jan 19 Co-authored-by: Ashton Huxtable <[email protected]> Co-authored-by: forstisabella <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: Sarah Rudy <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: bobbyatsegment <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Xavier Vello <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Spencer Attick <[email protected]>
markzegarelli
pushed a commit
that referenced
this pull request
Jan 19, 2023
* Analytics Node Next * edits * Apply suggestions from code review * edits * more edits * edits * [netlify-build] * What to do when credentials have updated/changed * add details about data type mismatch * update faq with data type * Update faq.md * Add information about deleting/changing ExternalID's * edits [netlify-build] * updated faq * reverted data types to list * Added troubleshooting section, edited explanatio * Developer Center 2.0 documentation (#4007) * Init * Intro edits * Draft complete * Apply suggestions from code review Co-authored-by: forstisabella <[email protected]> * Remove * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Clarifications from Sharan * No longer in Dev preview Co-authored-by: forstisabella <[email protected]> * edits [netlify-build] * Update Amplitude Classic Destination DOC-629 * Update EU Endpoint Language DOC-629 * Update index.md Add note about the API Key being region specific * Revert commit * Add section highlighting User Data parameter mappings to Facebook Conversions API Destination (#4025) * Update index.md * Update src/connections/destinations/catalog/actions-facebook-conversions-api/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: markzegarelli <[email protected]> * edits * added react native quick link * add section for api token security * update copy * Small edits * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * [netlify-build] * Update vale rules (#4055) * posthog: update instructions for Cloud EU * Add Audiences and Journeys Guide [netlify-build] * add correct actions slug (#4060) Co-authored-by: Niall Brennan <[email protected]> * Add platform code for setting writekey (#4050) * add platform code * add platform code * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: markzegarelli <[email protected]> * add info about how data comes from Clearbit (#4040) * add info about how data comes from Clearbit Customers in the past have been confused about dataflow with Clearbit and about why they see analytics-ruby events in their Debugger. This update clarifies that a bit. There are past Zendesk tickets that all confirm Clearbit data comes back to Segment using analytics-ruby. In addition, Clearbit published this line about it in one of their blog posts: https://clearbit.com/blog/enterprise-grade-analytics-for-startups-2#:~:text=Segment%E2%80%99s%20robust%20API%20and%20Ruby%20library%20enabled%20our%20engineering%20team%20to%20quickly%20build%20an%20event%20emitting%20service%20that%20sends%20usage%20and%20behavioral%20data%20from%20Clearbit%20applications%20and%20services%20into%20Segment%2C%20tracking%20everything%20from%20API%20usage%20and%20page%20views%20to%20signups%20and%20subscribe%20events.. * Update src/connections/destinations/catalog/clearbit-reveal/index.md Co-authored-by: markzegarelli <[email protected]> * edits * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * catalog update (#4064) * Added Proxy Sources Note cccccbbujrtrjbcnildcbuhchngfgrccvnuugiufffcl * Add new product limits for Engage (#3965) * Updating to exclude authenticating via email/token because it doesn't work (#4045) * Updating to exclude authenticating via email/token * Update src/connections/destinations/catalog/zendesk/index.md Co-authored-by: markzegarelli <[email protected]> * Clarify setup instructions Co-authored-by: Sai Gattu <[email protected]> Co-authored-by: markzegarelli <[email protected]> * Add links to Braze Swift and Kotlin plugin repositories (#4058) * Update index.md * Update src/connections/destinations/catalog/braze/index.md Co-authored-by: markzegarelli <[email protected]> * Update Public API docs to highlight eligibility for PAPI access (#4036) * Update index.md * Add plan grid to Public API page Co-authored-by: markzegarelli <[email protected]> * Apply suggestions from code review * Add a note that some Actions-based destinations do not support IE11 (#4066) * Update supported-browsers.md Actions destinations not yet supported for IE11 * Update src/connections/sources/catalog/libraries/website/javascript/supported-browsers.md Co-authored-by: markzegarelli <[email protected]> * Update index.md (#4047) Add Segment's GitHub repo to page * Apply suggestions from code review Co-authored-by: markzegarelli <[email protected]> * Add Amplitude Session ID Info #3972 * Fix Youbora Destination Typos * Add External Link * Update src/profiles/faqs.md * updated sentence for clarity * Unhide commandbar docs * Update src/connections/destinations/catalog/actions-amplitude/index.md Co-authored-by: stayseesong <[email protected]> * Update src/connections/destinations/catalog/actions-amplitude/index.md Co-authored-by: stayseesong <[email protected]> * Update src/connections/destinations/catalog/youbora/index.md Co-authored-by: stayseesong <[email protected]> * Update src/connections/destinations/catalog/youbora/index.md Co-authored-by: stayseesong <[email protected]> * Update src/connections/sources/catalog/libraries/server/node/index.md * Add device id config option for RN. (#4082) * add correct actions slug * add config option Co-authored-by: Niall Brennan <[email protected]> * Update language (#4077) * Update language * Update src/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md Co-authored-by: forstisabella <[email protected]> Co-authored-by: forstisabella <[email protected]> * Mention that the A.js snippet has version history available on GitHub (#4072) * Update 02-simple-install.md * Update src/getting-started/02-simple-install.md Co-authored-by: markzegarelli <[email protected]> * Update src/getting-started/02-simple-install.md Co-authored-by: markzegarelli <[email protected]> * Mention that an A.js snippet must be added to each subdomain (#4067) * Update index.md * Update src/connections/sources/catalog/libraries/website/javascript/index.md Co-authored-by: markzegarelli <[email protected]> * Add guidance around the number of sources a user should create (#4053) * Update index.md Add info block about whether customer should set up one source or multiple sources * Update src/connections/sources/index.md Co-authored-by: markzegarelli <[email protected]> * Update src/connections/sources/index.md Co-authored-by: markzegarelli <[email protected]> * Update src/connections/sources/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: markzegarelli <[email protected]> * Update index.md (#4044) * Update on choosing the Intercom workspace (#4019) * Update on choosing the Intercom workspace There is no information on how to choose the Intercom workspace to access. Hence, updating the information in step 5 of ## Getting started. Statement added as below: Select the Intercom workspace to access from a dropdown list beside the statement "Segment wants to access". * Update index.md As advised by Spencer in Jira ticket https://segment.atlassian.net/browse/KCS-32, replace: "Select the Intercom workspace to access from a dropdown list beside the statement "Segment wants to access with "If you have multiple Intercom workspaces, please choose the one that you'd like to connect to Segment" * Update src/connections/destinations/catalog/actions-intercom-cloud/index.md Co-authored-by: markzegarelli <[email protected]> * Update src/connections/sources/catalog/libraries/server/node/migration.md * Update src/connections/storage/warehouses/schema.md * Add info note specifying supported data types for mapping operators (#4078) * Update actions.md * Move data into a table to improve readability Co-authored-by: markzegarelli <[email protected]> * 20230119 catalog (#4084) * Release 23.3.2 (#4071) * Update faq.md * Developer Center 2.0 documentation (#4007) * Init * Intro edits * Draft complete * Apply suggestions from code review Co-authored-by: forstisabella <[email protected]> * Remove * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Update src/partners/index.md Co-authored-by: forstisabella <[email protected]> * Clarifications from Sharan * No longer in Dev preview Co-authored-by: forstisabella <[email protected]> * Update Amplitude Classic Destination DOC-629 * Update EU Endpoint Language DOC-629 * Update index.md Add note about the API Key being region specific * Revert commit * Add section highlighting User Data parameter mappings to Facebook Conversions API Destination (#4025) * Update index.md * Update src/connections/destinations/catalog/actions-facebook-conversions-api/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: markzegarelli <[email protected]> * added react native quick link * add section for api token security * update copy * Small edits * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * Update src/api/public-api.md Co-authored-by: stayseesong <[email protected]> * Update vale rules (#4055) * posthog: update instructions for Cloud EU * Add Audiences and Journeys Guide [netlify-build] * add correct actions slug (#4060) Co-authored-by: Niall Brennan <[email protected]> * Add platform code for setting writekey (#4050) * add platform code * add platform code * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> * Update src/connections/sources/catalog/libraries/mobile/react-native/index.md Co-authored-by: markzegarelli <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: markzegarelli <[email protected]> * add info about how data comes from Clearbit (#4040) * add info about how data comes from Clearbit Customers in the past have been confused about dataflow with Clearbit and about why they see analytics-ruby events in their Debugger. This update clarifies that a bit. There are past Zendesk tickets that all confirm Clearbit data comes back to Segment using analytics-ruby. In addition, Clearbit published this line about it in one of their blog posts: https://clearbit.com/blog/enterprise-grade-analytics-for-startups-2#:~:text=Segment%E2%80%99s%20robust%20API%20and%20Ruby%20library%20enabled%20our%20engineering%20team%20to%20quickly%20build%20an%20event%20emitting%20service%20that%20sends%20usage%20and%20behavioral%20data%20from%20Clearbit%20applications%20and%20services%20into%20Segment%2C%20tracking%20everything%20from%20API%20usage%20and%20page%20views%20to%20signups%20and%20subscribe%20events.. * Update src/connections/destinations/catalog/clearbit-reveal/index.md Co-authored-by: markzegarelli <[email protected]> * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * catalog update (#4064) * Add new product limits for Engage (#3965) Co-authored-by: Ashton Huxtable <[email protected]> Co-authored-by: forstisabella <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: Sarah Rudy <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: bobbyatsegment <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Xavier Vello <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Spencer Attick <[email protected]> * Catalog update for Jan 19 Co-authored-by: Ashton Huxtable <[email protected]> Co-authored-by: forstisabella <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: Sarah Rudy <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: bobbyatsegment <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Xavier Vello <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Spencer Attick <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: stayseesong <[email protected]> Co-authored-by: Dery J. Aldeano <[email protected]> Co-authored-by: Atif Javed <[email protected]> Co-authored-by: Ashton Huxtable <[email protected]> Co-authored-by: Olesia <[email protected]> Co-authored-by: forstisabella <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: Sarah Rudy <[email protected]> Co-authored-by: pwseg <[email protected]> Co-authored-by: bobbyatsegment <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: Sal Olivares <[email protected]> Co-authored-by: Xavier Vello <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Niall Brennan <[email protected]> Co-authored-by: Spencer Attick <[email protected]> Co-authored-by: Jazma Foskin <[email protected]> Co-authored-by: Sai <[email protected]> Co-authored-by: Sai Gattu <[email protected]> Co-authored-by: Thomas Gilbert <[email protected]> Co-authored-by: tanjinhong72 <[email protected]>
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.
Proposed changes
Add FAQ for how to set a specific writekey based on platform.