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

copy grol's workflow #16

Merged
merged 3 commits into from
Jul 20, 2024
Merged

copy grol's workflow #16

merged 3 commits into from
Jul 20, 2024

Conversation

ldemailly
Copy link
Member

No description provided.

@ldemailly ldemailly merged commit 6e11695 into main Jul 20, 2024
1 check passed
@ldemailly ldemailly deleted the workflows branch July 20, 2024 00:11
tags:
# so a vX.Y.Z-test1 doesn't trigger build
- 'v[0-9]+.[0-9]+.[0-9]+'
- 'v[0-9]+.[0-9]+.[0-9]+-pre*'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 'v[0-9]+.[0-9]+.[0-9]+-pre*'
- 'v[0-9]+.[0-9]+.[0-9]+-pre.*'

Otherwise you accept only pr, pre and variation of preeeeee

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank I fixed that bug in fortio/workflows but when I copied pre workflow files from multicurl I forgot about, nice catch

push:
tags:
# so a vX.Y.Z-test1 doesn't trigger build
- 'v[0-9]+.[0-9]+.[0-9]+'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would have expected to see a $

Suggested change
- 'v[0-9]+.[0-9]+.[0-9]+'
- 'v[0-9]+.[0-9]+.[0-9]+$'

Because otherwise the second regexp is useless, but also it lets me think this regexp is catching the -test tags you talk about

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought it's a full match but given pre1,2 etc did build, probably not

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's weird and I'll admit, don't have time to figure out but... it works grol-io/grol#51

Comment on lines +27 to +28
go-version: '1.22'
check-latest: true

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think providing the second implies the first one is useless

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no it stays on 1.22 (1.21 before) even when 1.23 ships

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