However I suggest that you create new DockerHub OWASP SAMM profile and we upload the image there (we can do it in Lisbon next week). After that we should change the workflow yaml file to use the new image.
After this pull request markdown generation will work as designed - when pushing a new "tag" or manually triggered by the "Actions" tab - "Generate web markdown". Markdown will be generated on a new branch that starts with "markdown/..."
Fixes #155
Two problems were fixed -
1.There are trailing whitespaces in two yaml files which are causing the "lintModelv20" job to fail.
2.The markdown generation uses docker image which has an issue (see https://github.com/owaspsamm/process-yaml-content/issues/4). I have created new docker image with the fix and released it under my DockerHub profile. I tagged it as "latest" because there is no newer version than v0.8.1 (see https://github.com/owaspsamm/process-yaml-content/issues/7). When a version for the yaml processor is created I can tag the image with the appropriate number.
However I suggest that you create new DockerHub OWASP SAMM profile and we upload the image there (we can do it in Lisbon next week). After that we should change the workflow yaml file to use the new image.
After this pull request markdown generation will work as designed - when pushing a new "tag" or manually triggered by the "Actions" tab - "Generate web markdown". Markdown will be generated on a new branch that starts with "markdown/..."