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

chore(ci): don't run lint-test before release in release workflow #1232

Merged
merged 1 commit into from
Jan 22, 2025

Conversation

pmalek
Copy link
Member

@pmalek pmalek commented Jan 22, 2025

What this PR does / why we need it:

lint-test is already run as part of each PR's CI so not point to wait another 20 minutes before releasing a chart.

Which issue this PR fixes

(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

  • fixes #

Special notes for your reviewer:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

  • PR is based off the current tip of the main branch.
  • Changes are documented under the "Unreleased" header in CHANGELOG.md
  • New or modified sections of values.yaml are documented in the README.md
  • Commits follow the Kong commit message guidelines

@pmalek pmalek added the area/ci label Jan 22, 2025
@pmalek pmalek self-assigned this Jan 22, 2025
@pmalek pmalek marked this pull request as ready for review January 22, 2025 11:33
@pmalek pmalek requested a review from a team as a code owner January 22, 2025 11:33
@pmalek pmalek enabled auto-merge (squash) January 22, 2025 11:33
@pmalek pmalek force-pushed the dont-lint-test-in-release-pipeline branch from b793dcb to 290d014 Compare January 22, 2025 11:35
@pmalek pmalek merged commit 4d734cb into main Jan 22, 2025
34 checks passed
@pmalek pmalek deleted the dont-lint-test-in-release-pipeline branch January 22, 2025 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants