-
Notifications
You must be signed in to change notification settings - Fork 23
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
Crispy-Salesforce
wants to merge
20
commits into
v7.20
Choose a base branch
from
W-17328723-Change-Design-Center-to-MuleSoftVCS-CP
base: v7.20
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
W-17328723-Change-Design-Center-to-MuleSoftVCS-CP #584
Crispy-Salesforce
wants to merge
20
commits into
v7.20
from
W-17328723-Change-Design-Center-to-MuleSoftVCS-CP
Conversation
This file contains 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
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
W-17328723-Change-Design-Center-to-MuleSoftVCS-CP
W-17328723-Change-Design-Center-to-MuleSoftVCS-CP
tomasperezc
requested changes
Dec 3, 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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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
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.
Writer's Quality Checklist
Before merging your PR, did you: