[Do Not Merge] DS-567: Remove Remaining bolt-button bolt-link #2450
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
# Conflicts: # packages/components/bolt-form/src/inputs/form-button.twig # packages/components/bolt-headline/__tests__/__snapshots__/headline.js.snap # packages/components/bolt-headline/src/_typography.twig
github-actions
bot
added
the
type: feature
…. update twig render endpoint test to use elements.
colbytcook
requested a deployment
to
feature/DS-567-remaining-button-link--bfeaea26--commit-preview
colbytcook
requested a deployment
to
feature/DS-567-remaining-button-link--branch-preview
colbytcook
requested a deployment
to
feature/DS-567-remaining-button-link--branch-preview
cjwhitedev
changed the title
cjwhitedev
changed the title
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.
Jira
https://pegadigitalit.atlassian.net/browse/DS-567
Summary
(Enter a one-line summary of the changes in this PR. This will be included in the release notes)
Details
(Explain the changes in enough detail fo reviewers to understand. Raise any questions for reviewers to consider.)
How to test
(List clear steps to test that the changes are working)
Release notes
(Optionally, add details that will be added to the release notes. Use this to call out deprecations. Read more)
Visual changes
(Note any visual changes associated with this PR. This will be shared with QA team for VRT.)