workflow: ignore v** tags #842
Conversation
this is an attempt to exempt the whole build workflow (and respective releases from being created) for upstream tags.
|
@helgeerbe Are you okay with this? I would assume so, since we discussed already that we indeed do not want to publish releases for upstream tags? |
|
Not to publish. But the the tag has to be maintained. It's used to refer to the upstream version, which our release is build on. |
|
Yes, we will still create the tag to name the respective commit, but there will be no re-build of the firmware for that tag and no release as part of this project. |
|
@helgeerbe This also does not work as intended. Look here: https://github.com/helgeerbe/OpenDTU-OnBattery/actions/runs/8944133856 See the "workflow file" under "run details" on the left. This is not our workflow file, it's the upstream workflow file. So, since we keep pushing upstream tags, which point to upstream commits and upstream versions of the repo, the build run will be triggered with the respective upstream workflow file, which does not have our filter (obviously). I guess we should resort to deleting such releases. Or we could abort the github actions after pushing upstream commits, which would be better, as no release is created and no emails alerting about the new release are generated. |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns. |
this is an attempt to exempt the whole build workflow (and respective releases from being created) for upstream tags.
inspired by https://github.com/orgs/community/discussions/25615.