Enhancement: Release -> Tweet

whiletruedoio / tooling

Overview and documentation of the tooling used to drive while-true-do.io. Also, integrations from one service to another.

BSD 3-Clause "New" or "Revised" License

2 stars 0 forks source link

Enhancement: Release -> Tweet #1

Open dschier-wtd opened 2 years ago

dschier-wtd commented 2 years ago

As a product owner, I want to inform twitter followers about new releases of repositories, so they can see it in the timeline.

Acceptance Criteria:

each new release triggers a tweet
optional customizable text
free for open source / github public repositories
saas solution

Deliverables:

New document created describing the solution
PoC repo created to demonstrate behavior
account created or requested (support via @daniel-wtd )

References:

automate.io (has an app for github)
zapier.com (already used to push blog posts)

dschier-wtd commented 2 years ago

zapier.com and automate.io also have integrations for slack

dschier-wtd commented 2 years ago

Zapier does not support tags, but only GitHub releases and you need one action per repository :/

dschier-wtd commented 2 years ago

automate.io has the same limitations... meh

pdq21 commented 2 years ago

How about Send Tweet Action? Maybe replace on: [push] ... with

on:
 release:
  type[s]: [published[,created,edited]]
  tags:
   - tag A
  jobs:
   tweet:
    runs-on: ubuntu-latest
    steps:
     - uses: ethomson/send-tweet-action@v1
      with:
       status: "We proudly present release ${{ github.ref }} with tag ${{ github.event.release.tag_name }}."
       ...

Did you have a look at Integromat's GitHub App? It also does not appear to look at tags of new releases. Unfortunately there seems to be no free tier for MS PowerAutomate despite Actions running on Azure Pipeline.

pdq21 commented 2 years ago

References for Webhook payload object for release, release object and access to object context ${{}}.

dschier-wtd commented 2 years ago

Actions are an option, too.

Biggest issue I can see: it must be added and adjusted in each and every repository and can't be done organization-wide. In the Ende the same problem as with Zapier or automate.

Furthermore, I am not planning to use the release feature, since tags are sufficient for basically everything and can be integrated in a typical merge-workflow.