blog.frankel.ch/cherry-pick-automation-bash
Preview meta tags from the blog.frankel.ch website.
Linked Hostnames
9- 16 links toblog.frankel.ch
- 2 links tobsky.app
- 2 links totwitter.com
- 2 links towww.reddit.com
- 1 link togithub.com
- 1 link tomastodon.top
- 1 link towww.facebook.com
- 1 link towww.linkedin.com
Thumbnail

Search Engine Appearance
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
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
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- titleCherry-pick automation with Bash
- charsetutf-8
- X-UA-CompatibleIE=edge
- HandheldFriendlytrue
- viewportwidth=device-width, initial-scale=1.0
Open Graph Meta Tags
8- og:site_nameA Java geek
- og:typewebsite
- og:titleCherry-pick automation with Bash
- og:descriptionI 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:urlhttps://blog.frankel.ch/cherry-pick-automation-bash/
Twitter Meta Tags
7- twitter:cardsummary_large_image
- twitter:site:idnicolas_frankel
- twitter:titleCherry-pick automation with Bash
- twitter:descriptionI 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:urlhttps://blog.frankel.ch/cherry-pick-automation-bash/
Item Prop Meta Tags
10- nameNicolas Fränkel
- givenNameNicolas
- familyNameFränkel
- jobTitleHead of Developer Advocacy
- worksForApache APISIX
Link Tags
12- alternatehttps://blog.frankel.ch/feed.xml
- urlhttps://blog.frankel.ch/cherry-pick-automation-bash/
- mehttps://mastodon.top/@frankel
- mehttps://github.com/nfrankel
- shortcut icon/assets/cup.ico
Links
27- http://www.reddit.com/submit?url=https://blog.frankel.ch/cherry-pick-automation-bash/&title=Cherry-pick automation with Bash
- https://blog.frankel.ch
- https://blog.frankel.ch/books
- https://blog.frankel.ch/cdn-cgi/l/email-protection
- https://blog.frankel.ch/creating-git-shortcuts