-
Notifications
You must be signed in to change notification settings - Fork 8
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
Release/v0.6.0: Redesign of Battery Passport #16
Release/v0.6.0: Redesign of Battery Passport #16
Conversation
fix: fixed backend configuration, re-enable response indent
…ry-passport Release/v0.6.0.0: Merge redesign battery pass
️✅ There are no secrets present in this pull request anymore.If these secrets were true positive and are still valid, we highly recommend you to revoke them. 🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request. |
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.
You do have a lot of copyright header findings again. Please use your IDE capabilities. It just takes too much time for a task, that could have been automated
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.
Copyright and License Header missing. Consider to use your IDE capabilities to auto-add them on new files
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.
Copyright + License header
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.
Header again
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.
Header
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.
This license header does not seem to be complete.
At lease SPDX identifier missing. Eclipse contributors part missing
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.
Again incomplete header
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.
Incomplete header
@matbmoser can you also please ask someone to do a content review, since I cannot review the CSS and JavaScript changes. |
@SebastianBezold We are aware of that... Unfortunately not all our developers have an automatic header license configured so we need to revise all manually and sometimes some files scape our control. They will be fixed. I will be reminding them to integrate the IDE header licenser. |
GitGuardian is detecting false positives in the values.yaml |
Is there any advice, that you can generally share? I could show you how i configured my IDEs from the JetBrains family. Not sure about VS Code in case you use that |
@SebastianBezold I will ask the question today in the DevSecOps meeting, I have it configured in Intelij however mostly we use VSCode and the structure by the plugins provided limits us (because it does not includes the SPDX field and the license notice at the same time) |
@SebastianBezold I just created a open discussion about that in the tractus-x dev mailing list, so we can find the best practices in this case. |
@SebastianBezold we solved the necessary fixes for the license headers in the last PR from the version v0.6.0 -> #24 |
Hi @SebastianBezold, I have reviewed the JavaScript and CSS content and they are fine and ready for the release v0.6.0. |
Sub release strategy (slit bigger releases) proposed by the System Team failed to work, because of lack of tracking and the lack of rebase possibilities. https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow The new commit strategy will follow this diagram from gitflow: |
Merging without copyright headers, but tracking in #24 |
Changes will be introduces in later PR
PR part of release v0.6.0, Sub Release v0.6.0.0
Why we create this PR?
To merge the new redesign passport changes
What we want to achieve with this PR?
Upgrade the actual design of the passport
What is new?
Added