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

[ 2° ] - Relaease/v2.2.0 battery composition graph #255

Conversation

davidzynda
Copy link
Contributor

Why we create this PR?

Cell chemistry section contains MOCKed battery graph with SVG file

What we want to achieve with this PR?

Code the Battery graph

What is new?

##Added

Coded Battery graph

@davidzynda davidzynda added the frontend Issue or PR connected to the frontend application label Mar 22, 2024
charts/digital-product-pass/templates/secret-backend.yaml Dismissed Show dismissed Hide dismissed
charts/digital-product-pass/templates/secret-backend.yaml Dismissed Show dismissed Hide dismissed
charts/digital-product-pass/templates/secret-backend.yaml Dismissed Show dismissed Hide dismissed
charts/digital-product-pass/templates/secret-backend.yaml Dismissed Show dismissed Hide dismissed
@saudkhan116 saudkhan116 modified the milestones: v2.2.0, v2.3.0 Mar 26, 2024
Copy link
Contributor

@matbmoser matbmoser left a comment

Choose a reason for hiding this comment

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

OSS license checks runned no restricted license!
Good to go

@saudkhan116 saudkhan116 merged commit abc6367 into eclipse-tractusx:main Mar 26, 2024
7 checks passed
@saudkhan116 saudkhan116 deleted the relaease/v2.2.0-battery-composition-graph branch March 26, 2024 14:39
saudkhan116 added a commit that referenced this pull request May 10, 2024
…idelines

chore/quality gate/release guidelines: updated docs to align with TRGs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
frontend Issue or PR connected to the frontend application
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants