-
Notifications
You must be signed in to change notification settings - Fork 135
Introduce verify target #930
Copy link
Copy link
Closed
Labels
area/ops-productivityOperator productivity related (how to improve operations)Operator productivity related (how to improve operations)kind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extensionlifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/3Priority (lower number equals higher priority)Priority (lower number equals higher priority)
Description
Metadata
Metadata
Assignees
Labels
area/ops-productivityOperator productivity related (how to improve operations)Operator productivity related (how to improve operations)kind/enhancementEnhancement, improvement, extensionEnhancement, improvement, extensionlifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.priority/3Priority (lower number equals higher priority)Priority (lower number equals higher priority)
How to categorize this issue?
/area ops-productivity
/kind enhancement
/priority 3
What would you like to be added:
Currently we have three separate make targets that we want to run before we merge a PR or say that a PR is ready to be consumed
Since we need all three to run and pass, we can combine them into a single target
make verify. This target should run all the above mentioned make targetsWhy is this needed:
This is needed to consolidate multiple make targets. This will also get us to simplify our pipeline definitions as it gives us one step to configure instead of 3 and hence only one golang version needs to be specified and this can be moved to
branch.cfgChanges/PRs to be filed to close this story