-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
TEP-0142: Introduce feature flag enable-step-actions
#7277
TEP-0142: Introduce feature flag enable-step-actions
#7277
Conversation
This PR introduces the feature flag `enable-step-actions`. The follow up PRs will use this feature flag to gate the validation logic.
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/assign |
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.
thanks for breaking it down @chitrangpatel
@tektoncd/core-maintainers please take a look
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JeromeJu, jerop, Yongxuanzhang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
/lgtm
enable-step-actions
enable-step-actions
This PR introduces the feature flag
enable-step-actions
. The follow up PRs will use this feature flag to gate the use ofStepActions
inTasks
.This is the second item on the implementation Issue #7259
Changes
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes
/kind feature