Skip to content
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

force push to gitlab #9

Merged
merged 3 commits into from
Apr 28, 2023

Conversation

bernt-matthias
Copy link
Contributor

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 ..

       --tags
           All refs under refs/tags are pushed, in addition to refspecs explicitly listed on the command line.

May fix #8

@bernt-matthias bernt-matthias marked this pull request as draft February 22, 2022 08:26
@bernt-matthias
Copy link
Contributor Author

Have to think a bit about it...

@bernt-matthias bernt-matthias marked this pull request as ready for review April 27, 2023 19:34
@bernt-matthias
Copy link
Contributor Author

bernt-matthias commented Apr 27, 2023

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

@mai00fti mai00fti merged commit ca9bb81 into yigbt:master Apr 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Push to GitLab action fails
2 participants