typescript-action VS get-changed-files

While learning about GitHub Actions, I came across the GitHub Actions Org, and they have a bunch of templates for building custom GitHub actions. So, I started searching for a template that has TypeScript support, ensuring type safety to write bug-free code. I found the typescript-action template that includes support for tests, linter, versioning, and more.

This is the template I used for my TypeScript action https://github.com/actions/typescript-action

I found the GitHub actions documentation easier to read than Azure, so I would recommend starting writing and testing your extensions on GitHub by using the official template actions/typescript-action. The mentioned template provides a good starting point; I won't repeat the steps here. Play with it, write some simple stuff, and then return here for the next steps.

GitHub maintain a set of repos called actions. One of which is called cache.

To get started quickly with a JavaScript action, I recommend using the official templates from GitHub for JavaScript and TypeScript.

On the TypeScript side, setup was much easier. There was already a template from GitHub that took care of the basics. Most of the time spent here was updating dependencies and getting my editor to play nicely with it—18 minutes, about 10% of the total.

Now that you know how to create your own GitHub Actions, why not give it a try? Head to the GitHub Marketplace and start exploring the existing Actions, or create your own and share it with the community. With GitHub Actions, the possibilities are endless, so start building and see what you can accomplish

Your build most likely fails because your tests fail. Most CI pipelines today, like Jenkins, Circleci, GitLab, TeamCity, Bamboo, and GitHub Actions, are configured to automatically cause the build process to fail when tests fail.

oh, apparently that was introduced in bash 4 and mac isn't there yet? https://github.com/jitterbit/get-changed-files/issues/15

[jitterbit/get-changed-files@v1](https://github.com/jitterbit/get-changed-files

# GitHub Action のプロジェクト名 name: 'Sync Zenn articles to DEV' # GitHub Action のプロジェクト説明文 description: 'Just sync Zenn articles to DEV.' # GitHub Action の作者 author: 'nikaera' # GitHub Action に渡せる引数の値定義 inputs: api_key: # フィールドの指定が必須であれば true、必須でなければ false を設定する # DEV の API キーは同期を行う際に必須なため、true を設定している required: true # フィールドの説明文 description: 'The api_key required to use the DEV API (https://docs.forem.com/api/#section/Authentication)' username: required: false description: "Zenn user's account name. (Fields to be filled in if canonical url is set.)" articles: required: false description: "The directory where Zenn articles are stored." # フィールドにはデフォルト値を指定することも可能 # Zenn の記事がデフォで格納されているフォルダ名を指定している default: articles update_all: require: false description: "Whether to synchronize all articles." default: true added_modified_filepath: required: false description: | Synchronize only the articles in the file path divided by line breaks. You can use jitterbit/get-changed-files@v1 to get only the file paths of articles that have changed in the correct format. (https://github.com/jitterbit/get-changed-files) # GitHub Action 実行後に参照可能になる値定義 outputs: articles: description: 'A list of URLs of dev.to articles that have been created or updated' newly-sync-articles: description: 'File path list of newly synchronized articles.' # GitHub Action の実行環境 runs: using: 'node12' # テンプレートプロジェクトでは コンパイル先が dist になるため `dist/index.js` を指定している main: 'dist/index.js'