Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the twister build is rebuilt automatically at the Docker hub as the twister-core Github repository is updated. But the build also adds twister-html from its separate Github repository. Unfortunately, that means the Docker image won't be automatically updated if twister-html is updated.
This is a request to change the situation. The plan:
Afterwards, every change to the twister-html repository will trigger a build of the new (dummy) twister-html image at the hub. As a result of that, a new build of the main twister image will be triggered. This means every change of either twister-core or twister-html will automatically create a new main image. Just what we want!
@miguelfreitas, as you are the owner of both the repositories, you are the only one who is able to set this up at the Docker hub. Would be cool if you found some time for that. Thanks in advance!