Automation for interacting with Tekton twitter account via gitops

[bobcatfish]

Okay so just like #38 but about our Twitter account instead!! https://twitter.com/tektoncd

At the moment only a few folks have access to the twitter account, and this means when there are announcements such as https://twitter.com/chmouel/status/1168821072441090048 they have to come from ppl's personal accounts (thanks @chmouel !) and get retweeted by the tektoncd account.

It would be very cool if folks working on Tekton could make new tweets by opening and merging pull requests.

Open question(s): not sure how to represent actions like "liking" and retweeting other random tweets. Also don't want to block folks from using the Twitter account directly? (Or it will probably never be used to retweet anything) - maybe something can be done to reconcile the state of the twitter account with the repo periodically?

[jlpettersson]

It would be very cool if folks working on Tekton could make new tweets by opening and merging pull requests.

Yes, sounds very cool. And we could start with this functionallity.

Open question(s): not sure how to represent actions like "liking" and retweeting other random tweets. Also don't want to block folks from using the Twitter account directly? (Or it will probably never be used to retweet anything) - maybe something can be done to reconcile the state of the twitter account with the repo periodically?

We can think about this and do that in other iterations?

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

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.

[bobcatfish]

No one has gotten to this yet but I still think it's important to open up community resources such as the twitter account so that it's clear how to use them and more than just a select few have access

/lifecycle frozen