-
Notifications
You must be signed in to change notification settings - Fork 2
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
(feat): reuseable workflows for static puml / mermaid files #164
Conversation
do | ||
mmdc -i $file -o ${file%.*}.svg | ||
echo "${file%.*}.svg" | ||
git add ${file%.*}.svg |
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.
I am unsure, what this is doing. git add
, without commit? Is this needed, it there is an git-auto-commit-action
In general I still think, that it is not a good idea to autocommit things that where generated from a PR.
The minimal change, that I would want to see here, is an environment variable that controls, whether or not the auto-commit is done. It should default to false
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.
at this step it will only staged, in case of there are more files that have changes.
At the current point this workflow just keep the static files updated.
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.
---
title: workflow currently works
---
flowchart TD
A[Reason: I want to change puml / mmd ] --> B(create PR)
B --> C(someone approve pr on codelines)
C --> D(merge pr)
D --> E(Workflow checks that there are changed puml/mmd codefiles)
E --> F(workflow provides new static files )
F --> G(update static files on main)
…167) - add example workflows to check dependencies for yarn and dotnet the workflows also provide a quite easy option to update the DEPENDENCIES file (without committing on the feature branch via bot or opening another PR, I didn't like both options): once all the previous step were successful so that no restricted dependencies are in the DEPENDENCIES file anymore, the last step uploads the updated DEPENDENCIES file to the workflow as downloadable artifact which can then be easily committed.
feat: add `run-dash` action to analyze 3rd party dependencies
…es as job artifact
+ adapt README.md references
…es as job artifact
…files' into feat/reuseable_workflows_static_files # Conflicts: # README.md
Description
.svg
-files from found mermaid files.svg
-files from found plantuml filesReadMe.md
quality check
.github/workflows/reusable-generate-mermaid-svg.yaml
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:
FaGru3n, Mercedes-Benz Tech Innovation GmbH, legal info/Impressum