-
Notifications
You must be signed in to change notification settings - Fork 347
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
Limit GHA to main and release branches #86
Conversation
Signed-off-by: Arko Dasgupta <arko@tetrate.io>
@@ -1,10 +1,16 @@ | |||
name: Build and Test | |||
on: | |||
push: | |||
branches: | |||
- "main" | |||
- "release-v*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
release/*
for consistency w/envoy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we've already started with release-v0.1.0
(https://github.com/envoyproxy/gateway/tree/release-v0.1.0)
@danehans any idea why we picked this convention ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can rename branches anyway
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@arkodg I used Envoy as the model for Gateway release branch naming, substituting /
with -
since -
is more widely used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool thanks, I'll leave the PR as is, since the naming was intentional, we can change it, if we change the branch naming in the future
Limit GHA to main and release branches (envoyproxy#86)
xref #63 |
Signed-off-by: Arko Dasgupta arko@tetrate.io