Add v.1 of the workflow for annunce posts on social.

[giulianolatini]

The workflow publishes on social networks from the annunce.data file. This file is generated by Hugo when publishing the static site. In annunce.data are presented the most recent posts that are published. The workflow reads annunce.data, generates parallel jobs when the site announces more than one post. The post has its own job. The message generated from the post is sent on one or more social networks. This v.1 workflow publishes only on Twitter.

To run publish-on-social workflow define and set these Github Secrets:

• GLV_SITE_ANNOUNCE_DATA: URL to read the annunce.data file
• TWITTER_CONSUMER_API_KEY: token get from developer.twitter.com
• TWITTER_CONSUMER_API_SECRET: token get from developer.twitter.com
• TWITTER_ACCESS_TOKEN: token get from developer.twitter.com
• TWITTER_ACCESS_TOKEN_SECRET: token get from developer.twitter.com

[giuliov]

I do not get how you want to integrate this.
My idea was to add this code as a custom action in the publish-on-master workflow, after Hugo completes generating. This way the announce files are available locally and you generate the tweet in sync with the published posts.

[giulianolatini]

When I start to develop the publish-on-master, my idea was to make an independent workflow. It will run four or five times into the week. I think of needed to repeat the announcement for Twitter's model. I have scared that the tweet post will be covered into twitter's flow. It's ok for me if we plan a different strategy, I remove GH Acton into the job where announce.data is read and It will change with Annunce-Data=$(cat ${{secrets.GLV_SITE_ANNOUNCE_DATA}}) and change the steps.read-announce-data.outputs.response with Annunce-Data. The secrets.GLV_SITE_ANNOUNCE_DATA change from ULR to repo path, of course.

I do not get how you want to integrate this.
My idea was to add this code as a custom action in the publish-on-master workflow, after Hugo completes generating. This way the announce files are available locally and you generate the tweet in sync with the published posts.

[giuliov]

I propose to simply merge this and see how it goes but we have to setup the secrets: @igoran I think only you can do it.