Tracking Issue for Zapier Automation of GitHub to Twitter

[Atharva-Shinde]

This issue is created to address and discuss the ongoing effort of building a new tweet automated solution using Zapier.

[Atharva-Shinde]

The Zapier automation could be a good replacement to our current contributor-tweets automation

[Atharva-Shinde]

/area contributor-comms

[imnmo]

Should existing workflow remain the same: Issue to PR to tweet and PR to tweet (to be discussed).

Existing features in the current code are :

• Zapier automation should run based on the specific issue label
• Tweet content length should be checked (follow max tweet length) - here is where /validate command is used
• Notify when something is fails

Some points from our weekly comms meeting:

• Editing for tweets be considered
• Favoured is PR to tweet and close the issue

[chris-short]

Zapier account created (by @mrbobbytables)

YouTube plugged in

Still need GDrive and Zoom connections and migration can be completed.

[kaslin]

@kaslin Look into this with @chris-short, see if you can help

[chris-short]

I need to start looking into a new GitHub -> Zap -> Buffer workflow.

[mrbobbytables]

Repo is being archived, going to go ahead and close this out. For more info, please see kubernetes/org#4481

/close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

Repo is being archived, going to go ahead and close this out. For more info, please see kubernetes/org#4481

/close

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/test-infra repository.