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

Merged

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
@Crispy-Salesforce
Copy link
Contributor Author

Hi, @tomasperezc! Please, can you look at the PR again? Thanks!

. In the *Create Branch* window, configure your new branch:
+
image::studio::create-new-branch.png[]
image::studio::create-new-branch.png["*Branch name* field, *Configure upstream for push and pull* option, and *Check out new branch* option highlighted in the *Create Branch* window".]
Copy link

@JennyHajee JennyHajee Dec 4, 2024

Choose a reason for hiding this comment

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

Do we need to use bold in Alt text since it's read by a screen reader?

Copy link
Contributor Author

@Crispy-Salesforce Crispy-Salesforce Dec 4, 2024

Choose a reason for hiding this comment

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

I use bold to avoid labels from being translated. Thanks for your comment!

@@ -18,15 +18,15 @@
** xref:import-api-specification-exchange.adoc[From Exchange]
** xref:import-api-specification-maven.adoc[From Maven]
** xref:import-api-specification-local-file.adoc[From a Local File]
** xref:import-api-specification-design-center.adoc[From Design Center]
** xref:import-api-specification-design-center.adoc[From MuleSoft VCS]

Choose a reason for hiding this comment

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

Is VCS an acronym for the product? If so, is it legally branded?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

See my comment in the thread. Thanks!

@Crispy-Salesforce Crispy-Salesforce merged commit 4548e83 into v7.20 Dec 4, 2024
5 checks passed
@Crispy-Salesforce Crispy-Salesforce deleted the W-17328723-Change-Design-Center-to-MuleSoftVCS-CP branch December 4, 2024 21:04
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.

3 participants