Skip to content

Conversation

@kevinmessiaen
Copy link
Member

Description

Show name of transformations performed in CTA

image

Type of Change

  • 📚 Examples / docs / tutorials / dependencies update
  • 🔧 Bug fix (non-breaking change which fixes an issue)
  • 🥂 Improvement (non-breaking change which improves an existing feature)
  • 🚀 New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to change)
  • 🔐 Security fix

@linear
Copy link

linear bot commented Oct 24, 2023

GSK-1916 The transformation push are hard to understand. We should clearly says what transformation we did

This is not clear

image.png

We should add in parenthesis the type of transformation we did (uppercase, typo, title case, etc.)

Copy link
Contributor

@Googleton Googleton left a comment

Choose a reason for hiding this comment

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

lgtm

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@mattbit mattbit merged commit a5369b5 into main Oct 25, 2023
@mattbit mattbit deleted the feature/gsk-1916-the-transformation-push-are-hard-to-understand-we-should branch October 25, 2023 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants