Notify comms team when a new issue is created

[mfahlandt]

Things we have already done:
update the k/community issues template to alert the team when a new marketing issue is created.
Template: https://github.com/kubernetes/community/blob/master/.github/ISSUE_TEMPLATE/marketing-request.yml

To tag our team, defined here: https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-contributor-experience/teams.yaml

Some other notes:
Looks possible to notify us on Slack via a “mention” in SIGS.yaml.
Sounds like CNCF does something similar with notifications about github activities, might be a good reference.

Prioritizing this as it should cover gap for PRs.

Contributor-comms team meeting: https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-contributor-experience/teams.yaml

How do other groups make sure they’re notified of PRs and issues?

Previous relevant PR:
PR: #6948

https://docs.github.com/en/actions/managing-issues-and-pull-requests/commenting-on-an-issue-when-a-label-is-added

Yash is interested in this
Chris actually knows things about how our Zapier is set up

How does sig-contribex-comms label work? Can we use it to notify us?

• Notifications on Github
• Notifications on Slack?

Have we done a blog on how to work with contributor comms? We should do this and decide how we want this to work.

• Ping us on slack is always an option
• How do we want folks to use github?

A conversation in Slack indicates that we should maybe abandon this for now.

Sujay is going to continue to look into this from a Zapier perspective.

Oct 13 - Might not required anymore

August 2 - Mario is implementing a new issue template.

[k8s-ci-robot]

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

• /sig <group-name>
• /wg <group-name>
• /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[mfahlandt]

Added Auto Tagging for Issues in PR #7900

[mfahlandt]

Todo: Update https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-contributor-experience/teams.yaml Comms Team

[mfahlandt]

/assign