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

W-17328723-Change-Design-Center-to-MuleSoftVCS-CP #584

Open
wants to merge 20 commits into
base: v7.20
Choose a base branch
from

Conversation

Crispy-Salesforce
Copy link
Contributor

Writer's Quality Checklist

Before merging your PR, did you:

  • Run spell checker
  • Run link checker to check for broken xrefs
  • Check for orphan files
  • Perform a local build and do a final visual check of your content, including checking for:
    • Broken images
    • Dead links
    • Correct rendering of partials if they are used in your content
    • Formatting issues, such as:
      • Misnumbered ordered lists (steps) or incorrectly nested unordered lists
      • Messed up tables
      • Proper indentation
      • Correct header levels
  • Receive final review and signoff from:
    • Technical SME
    • Product Manager
    • Editor or peer reviewer
    • Reporter, if this content is in response to a reported issue (internal or external feedback)
  • If applicable, verify that the software actually got released

@Crispy-Salesforce Crispy-Salesforce requested a review from a team as a code owner December 1, 2024 20:52
@Crispy-Salesforce Crispy-Salesforce changed the base branch from v7.19 to v7.20 December 1, 2024 20:52
@Crispy-Salesforce Crispy-Salesforce changed the title W 17328723 change design center to mule soft vcs cp W-17328723-Change-Design-Center-to-MuleSoftVCS-CP Dec 1, 2024
@@ -3,18 +3,18 @@ ifndef::env-site,env-github[]
include::_attributes.adoc[]
endif::[]

In certain scenarios, someone else might have modified the version in Design Center while you modified the same version locally. This triggers a conflict in git.
In certain scenarios, someone else can introduces changes in the version in MuleSoft VCS at the same time you modify the same version locally. This triggers a conflict in Git.

Choose a reason for hiding this comment

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

can introduces --> can introduce

You can either create and publish an API specification with the xref:design-center::design-create-publish-api-visual-editor.adoc[Visual Editor] or with the xref:design-center::design-create-publish-api-raml-editor.adoc[Text Editor].
. Import the API specification from Design Center into Studio. +
You can import the API specification as an editable asset by xref:sync-api-projects-design-center.adoc[Synchronizing an API Specifications with Design Center].
. Import the API specification from Design Center through MuleSoft VCS into Studio.

Choose a reason for hiding this comment

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

Should we change the from Design Center bit in here to from Anypoint Platform?

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.

2 participants