Merged
Conversation
Contributor
Author
|
Have to think a bit about it... |
and revert force push
Contributor
Author
|
ping @halirutan and @mai00fti .. I guess the problem was that the workflow was triggered on push events to any branch... Edit: bit confusing.. on: push has been removed meanwhile (since #8). So we can keep it as it is (ie only push on tag) or as suggested here Anyway we can close #8 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
If I get it right the last sync created a merge commit at hzdr which we did not have here at github.
So one option might be to have a pull after the push(es) in the action. The alternative (implemented here) is to force push which definitely overwrites everything at hzdr.
Not sure if we need both pushes ..
May fix #8