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: remove master-main sync workflow #1222

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

pmalek
Copy link
Member

@pmalek pmalek commented Jan 20, 2025

What this PR does / why we need it:

master doesn't seem used by anything anymore so let's remove the workflow that sync master to latest main.

After this PR merges we'll remove the master branch altogether

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 20, 2025
@pmalek pmalek self-assigned this Jan 20, 2025
@pmalek pmalek force-pushed the remove-master-branch-sync-workflow branch from cb47ef3 to dc5e462 Compare January 20, 2025 16:59
@pmalek pmalek marked this pull request as ready for review January 21, 2025 12:37
@pmalek pmalek requested a review from a team as a code owner January 21, 2025 12:37
@pmalek pmalek enabled auto-merge (squash) January 21, 2025 12:38
@pmalek pmalek merged commit 9d0c9a6 into main Jan 21, 2025
34 checks passed
@pmalek pmalek deleted the remove-master-branch-sync-workflow branch January 21, 2025 12:41
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