fix: update broken community meeting link in CONTRIBUTING.md#6506
Open
cheese-cakee wants to merge 2 commits intopipe-cd:masterfrom
Open
fix: update broken community meeting link in CONTRIBUTING.md#6506cheese-cakee wants to merge 2 commits intopipe-cd:masterfrom
cheese-cakee wants to merge 2 commits intopipe-cd:masterfrom
Conversation
eeshaanSA
requested changes
Feb 7, 2026
Signed-off-by: cheese-cakee <farzanaman99@gmail.com>
cheese-cakee
force-pushed
the
fix/broken-meeting-link
branch
from
8999492 to
1ac5b3d
Compare
Author
|
I have addressed the issue. please give it a check @eeshaanSA |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does:
Updates the community meeting link in CONTRIBUTING.md to point to the CNCF Slack channel, as the previous Zoom link was outdated/broken.
Why we need it:
New contributors were being directed to a dead link, causing confusion.
Which issue(s) this PR fixes:
Fixes #6499
Does this PR introduce a user-facing change?: