-
Notifications
You must be signed in to change notification settings - Fork 6
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
Git Harvest Plugin and Tutorial #256
Conversation
My idea is to open a new public repository named plugins/ and add harvest-git there. Then I would like to use this plugin in the workflow source code, so HERMES would actively use it. Update: you can't have group repos, so we decided for a name convention. Every plugins name should be hermes-plugin-{plugin name} |
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.
Mostly formatting, but some minor (content) changes are also proposed.
There is one line that tells the wrong story...
Co-authored-by: Michael Meinel <michael.meinel@dlr.de>
We should maybe keep the name convention hermes-plugin-git through the whole project and not change to hermes_git but to hermes_plugin_git |
Closes #255 .
This Feature shows a Tutorial for writing plugins for HERMES. To do that the git harvest plugin will be in another project.
Currently in https://github.com/hermes-hmc/hermes-git