-
Notifications
You must be signed in to change notification settings - Fork 54
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
jArchi pre-commit hook #183
Conversation
…himatetool.scripts.command.runScript"
…himatetool.scripts.command.runScript"
…lrepository-plugin into jarchi-hooks
Thanks for putting in the effort for this PR (ideally it should be a draft PR) We have to assume that not all coArchi users also use jArchi. Furthermore, coArchi and jArchi should know nothing of each other, so I see some problems with this and the other PR.
On the other PR (archimatetool/archi-scripting-plugin#100) the problems are:
What may be useful is the proposed jArchi Ideally the way to do something like this is:
And another consideration is that this may be more suited to coArchi 2. |
…himatetool.scripts.command.runScript"
…lrepository-plugin into jarchi-hooks
@dwinkler-oebb I'll close this PR for the reasons in the comment above. |
Hi @Phillipus,
This pull request is a following up my question in archimatetool/archi-scripting-plugin#77 (comment)
For realizing my envisioned Archi workflow it prepared this pull request since there is currently no integration of jArchi & coArchi.
This pull-request realizes the following:
Kind regards
Dominic