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

Clean leftover gitleaks; allow fourth version component outside of main #47

Merged
merged 5 commits into from
Jan 23, 2025

Conversation

ml-ebs-ext
Copy link
Contributor

The changes to functionality are restricted to the release.yml file.

I've tested the modified action manually by creating a draft PR targetting a main branch: https://github.com/Boehringer-Ingelheim/dv.listings/actions/runs/12931690475/job/36066883922
image
The action fails as it's supposed to.

Using the same repository in the same state, but without targetting the main branch of the repo, the four-component version number is accepted:
image

I've deactivated the DEBUG flag to reduce noise.

@ml-ebs-ext ml-ebs-ext requested a review from zsigmas January 23, 2025 15:11
@ml-ebs-ext ml-ebs-ext merged commit ca0ae36 into main Jan 23, 2025
12 checks passed
@ml-ebs-ext ml-ebs-ext deleted the allow_fourth_version_component branch January 23, 2025 15:54
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.

2 participants