blog-post-workflow VS starter-workflows

Now, we will create a new action for your repository. There is an awesome action template that can be used directly. This action will fetch the blogs from your Medium profile and put that on your GitHub profile page.

I would like to be able to add an RSS feed with latest posts to my github profile via https://github.com/gautamkrishnar/blog-post-workflow

Thanks to GitHub-flavored markdown, there's a lot you can do in your profile README. Mine has links to sites I've built, recordings of talks I've given, ways to connect, and a Blog Post Workflow written by @gautamkrishnar using Github Actions.

That space alloted labeled "Recent Updates" is meant to list scraped RSS or feed from any of my blogs. I used this Github Action.

Paste the code inside your yml file. Get the RSS feed URLs of your blog post sources and replace the feed list in the code above, indicated with an arrow. Visit this repository and scroll down to get the RSS feed URLs of some popular blogging platforms. Simply remove the links in the code above and paste yours in, separated by a comma if you have multiple sources. Don't remove the quotation marks.

The github action supports a readme_path parameter. After a quick dive in its source code I noticed that this file could be anything, not necessarily a markdown file. Problem solved!

As I planned to start blogging, I stumbled across this idea as I myself was looking to start a blogging presence of my own. As I looked around, I was able to only find one easy-to-use GitHub action that would allow me to add a list of my posts to my readme. Sadly, I was disappointed to discover that this action had little formatting, only setting up the posts as a bulleted list of links, which was less than appealing to the eye.

If you are active in writing blog posts, maybe you will want to add them to your readme profil page. Mine are not generated using some action because I have linked them to the repository concerned, but you can do it using blog-post-workflow (the description of how to use it are in the readme).

GitHub, as one of the leading web-based Git repository hosting service, provides a powerful suite of CI/CD tools in the form of GitHub Actions. These are directly integrated into the platform which empowers developers to increase the speed, efficiency and reliability of delivering products. In this brief article, we will take a look at what CI/CD is, why we should use it, as well as some of its applications in my projects.

GitHub Actions is a modern CI/CD tool integrated natively on GitHub. Itenables the rapid automation of build, test, deployment, and other custom workflows on GitHub with no need for external tools.

GitHub Actions is GitHub's CI/CD solution. You can use it to run automated tasks each time you change your code. Although the platform lacks a built-in Kubernetes integration, third-party plugins such as Azure's Deploy to Kubernetes Cluster action can automate deployments and manage different rollout strategies.

GitHub Actions is a feature-rich CI/CD platform embedded within GitHub, enabling developers to automate, customize, and execute software development workflows directly in their repositories. An Action inside GitHub Actions is a discrete unit of automation that performs a specific task within a workflow. All the Actions are reusable, and there are many to choose from. You can even create your own reusable ones.

actions/starter-workflows

The real power of using PHP code-quality tools is when it’s added to your continuous integration process, which means it automatically checks the code every time someone makes a push or pull request to your project repo. In this section, we'll be looking at how to do just that. GitHub actions is available for free so we'll use it for demo purposes. Note that there are some limits to private repos, so set your test repo to public if you can.

You can even automate the running of this script — hence the directory name automation — to happen every time the data changes, using GitHub Actions.

# Based on https://github.com/actions/starter-workflows/blob/main/ci/node.js.yml name: CI on: pull_request: branches: - main jobs: ci: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - uses: actions/setup-node@v2 with: node-version: lts/* cache: 'npm' - run: npm ci - run: npm run build --if-present - run: npm test

You might remember that I’ve been taking an interest in GitHub Actions for the last year or so (I even wrote a book on the subject). And at the Perl Conference in Toronto last summer I gave a talk called “GitHub Actions for Perl Development” (here are the slides and the video).