blog.frankel.ch/cherry-pick-automation-bash

Preview meta tags from the blog.frankel.ch website.

Linked Hostnames

9

Thumbnail

Search Engine Appearance

Google

https://blog.frankel.ch/cherry-pick-automation-bash

Cherry-pick automation with Bash

I manage my Jekyll blog in a Git repo. My publication process uses 2 branches: master contains all production content, and feature/newposts has the new blog posts, ready to get published, one commit per post. To publish an existing post: I check the to-be-published post in the feature/newposts branch. Then, get the associated commit. And cherry pick it in the master branch. Finally, I push.



Bing

Cherry-pick automation with Bash

https://blog.frankel.ch/cherry-pick-automation-bash

I manage my Jekyll blog in a Git repo. My publication process uses 2 branches: master contains all production content, and feature/newposts has the new blog posts, ready to get published, one commit per post. To publish an existing post: I check the to-be-published post in the feature/newposts branch. Then, get the associated commit. And cherry pick it in the master branch. Finally, I push.



DuckDuckGo

https://blog.frankel.ch/cherry-pick-automation-bash

Cherry-pick automation with Bash

I manage my Jekyll blog in a Git repo. My publication process uses 2 branches: master contains all production content, and feature/newposts has the new blog posts, ready to get published, one commit per post. To publish an existing post: I check the to-be-published post in the feature/newposts branch. Then, get the associated commit. And cherry pick it in the master branch. Finally, I push.

  • General Meta Tags

    9
    • title
      Cherry-pick automation with Bash
    • charset
      utf-8
    • X-UA-Compatible
      IE=edge
    • HandheldFriendly
      true
    • viewport
      width=device-width, initial-scale=1.0
  • Open Graph Meta Tags

    8
    • og:site_name
      A Java geek
    • og:type
      website
    • og:title
      Cherry-pick automation with Bash
    • og:description
      I manage my Jekyll blog in a Git repo. My publication process uses 2 branches: master contains all production content, and feature/newposts has the new blog posts, ready to get published, one commit per post. To publish an existing post: I check the to-be-published post in the feature/newposts branch. Then, get the associated commit. And cherry pick it in the master branch. Finally, I push.
    • og:url
      https://blog.frankel.ch/cherry-pick-automation-bash/
  • Twitter Meta Tags

    7
    • twitter:card
      summary_large_image
    • twitter:site:id
      nicolas_frankel
    • twitter:title
      Cherry-pick automation with Bash
    • twitter:description
      I manage my Jekyll blog in a Git repo. My publication process uses 2 branches: master contains all production content, and feature/newposts has the new blog posts, ready to get published, one commit per post. To publish an existing post: I check the to-be-published post in the feature/newposts branch. Then, get the associated commit. And cherry pick it in the master branch. Finally, I push.
    • twitter:url
      https://blog.frankel.ch/cherry-pick-automation-bash/
  • Item Prop Meta Tags

    10
    • name
      Nicolas Fränkel
    • givenName
      Nicolas
    • familyName
      Fränkel
    • jobTitle
      Head of Developer Advocacy
    • worksFor
      Apache APISIX
  • Link Tags

    12
    • alternate
      https://blog.frankel.ch/feed.xml
    • url
      https://blog.frankel.ch/cherry-pick-automation-bash/
    • me
      https://mastodon.top/@frankel
    • me
      https://github.com/nfrankel
    • shortcut icon
      /assets/cup.ico

Links

27