Automation for interacting with Tekton twitter account via gitops
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 406
- Forks
- 242
- Avg merge
- 23d 20h
- Merged PRs (30d)
- 1
Description
Okay so just like https://github.com/tektoncd/community/issues/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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing this issue with community issue #38, then map the requested pull-request workflow for the Tekton Twitter account. Resolve how tweets, likes, retweets, direct account use, and periodic reconciliation should be represented; no files or tests are named, so completion criteria are not yet defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100