-
Notifications
You must be signed in to change notification settings - Fork 38
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
feat(cascading): option to bypass non-latest minor branch #2473
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,6 +11,8 @@ export interface CascadingConfiguration { | |
defaultBranch: string; | ||
/** Pattern determining if the branch is part of the cascading strategy */ | ||
cascadingBranchesPattern: string; | ||
/** Determine if the branches for which a higher minor version exists should be skipped during the cascading */ | ||
onlyCascadeOnHighestMinors: boolean; | ||
/** Pattern containing a capture to extract the version of a cascading branch */ | ||
versionCapturePattern: string; | ||
/** Bypass the reviewers validation for the pull request, only the CI checks will be executed */ | ||
|
@@ -34,7 +36,10 @@ export interface PullRequestContext { | |
currentBranch: string; | ||
/** Cascading Pull Request Target Branch */ | ||
targetBranch: string; | ||
/** Determine if the reviewers are bypassed */ | ||
/** | ||
* Determine if the reviewers are bypassed | ||
* Note: This option is not supported on Github anymore due to Github Api change. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why are not we deprecating it ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I did not deprecate this option because I think that as the cascading is already today platform agnostic (event if it is implemented only for Github) and this option still make sense for supporting platform, it would be weird to remove it in 1 year to follow the unique implementation to potentially seeing it reappear after a while because of a new implementation. PS: To implement another platform support, there is no need to extract code, it's the bot that should switch the implementation according to the received message. So today it is already ready to support multi platform as it is |
||
**/ | ||
bypassReviewers: boolean; | ||
/** Is the an update of the {@link currentBranch} conflicting */ | ||
isConflicting: boolean; | ||
|
@@ -68,6 +73,7 @@ export const DEFAULT_CONFIGURATION: Readonly<CascadingConfiguration> = { | |
ignoredPatterns: [] as string[], | ||
defaultBranch: '', | ||
cascadingBranchesPattern: '^releases?/\\d+\\.\\d+', | ||
onlyCascadeOnHighestMinors: false, | ||
versionCapturePattern: '/((?:0|[1-9]\\d*)\\.(?:0|[1-9]\\d*)(?:\\.0-[^ ]+)?)$', | ||
bypassReviewers: false, | ||
labels: [] as string[], | ||
|
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 should probably not activate it for us
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.
Why ? I was thinking that it is actually the issue we have today with the non-removed prerelease branches and the policy supporting only the latest minor of each major?