Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more! Learn more →
Top 23 TypeScript github-action Projects
-
-
actions-gh-pages
GitHub Actions for GitHub Pages 🚀 Deploy static files and publish your site easily. Static-Site-Generators-friendly.
Check out the GitHub action you can use for deploying to GitHub pages: https://github.com/peaceiris/actions-gh-pages.
-
Appwrite
Appwrite - The Open Source Firebase alternative introduces iOS support . Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!
-
github-pages-deploy-action
🚀 Automatically deploy your project to GitHub Pages using GitHub Actions. This action can be configured to push your production-ready code into any branch you'd like.
Project mention: How to publish React App (CRA) on Github Pages using Github Actions with Turborepo | dev.to | 2023-03-16Finally, will do the deploy on github pages using the scripts from JamesIves/github-pages-deploy-action, and create a branch gh-pages with the code from apps/web/build.
-
Project mention: Where do you commit files for containers that run CI scripts? | reddit.com/r/devops | 2023-03-29
Docker made some decent actions free to use like this one to build and push docker images to registries.
-
Project mention: How to Automatically Update Resume On Your Personal Site From OverLeaf | dev.to | 2023-03-27
Create a new workflow, and then enter the code below. This code will create the PDF version of the latex file with every push into this repository. Each push will create a new release of your resume's latest iteration, and it will be an artifact attached to this. You may encounter an error based off the permission of the GitHub Action but this issue is explained well in this post.
-
-
setup-php
GitHub action to set up PHP with extensions, php.ini configuration, coverage drivers, and various tools.
I found shivammathur/setup-php did a better job on supporting old PHP versions, and you don't have to worry about the composer & extension compatibility, it handles those for you.
-
InfluxDB
Access the most powerful time series database as a service. Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.
-
snk
🟩⬜ Generates a snake game from a github user contributions graph and output a screen capture as animated svg or gif
There are, of course more elements to make an action. But still, I am a beginner. I am currently using Platane/snk dependency for a nice snake animation on my README.md.
-
ts-nextjs-tailwind-starter
🔋 Next.js + Tailwind CSS + TypeScript starter and boilerplate packed with useful development features
-
-
-
actions-hugo
GitHub Actions for Hugo ⚡️ Setup Hugo quickly and build your site fast. Hugo extended, Hugo Modules, Linux (Ubuntu), macOS, and Windows are supported.
You can build your Hugo site in your Github Actions, e.g. like in https://github.com/peaceiris/actions-hugo, then push the static pages to your server
-
paths-filter
Conditionally run actions based on files modified by PR, feature branch or pushed commits
If that isn’t sufficient, there are a number of third party workflow steps that enable conditional builds with extra flexibility like https://github.com/dorny/paths-filter
-
-
Workflows that interact with the Github API heavily will fail as they're not available in act e.g. actions like https://github.com/styfle/cancel-workflow-action. Dealing with secrets is also a bit cumbersome. You can throw the following on actions that are not compatible with act in order to skip them:
if: ${{ !env.ACT }}
That said, despite it's limitations, I've been using both act and tmate in combination for a couple of years. Gets the job done.
-
I have been using osmo feed [0]. Rather than self hosting, it uses GitHub actions. I have my own usename.github.io/to-read linked to it, to access it from anywhere. So far I have liked this approach.
-
add-and-commit
:octocat: Automatically commit changes made in your workflow run directly to your repo
Project mention: vim-dirtytalk: spellcheck dictionary for programmers 📖 | reddit.com/r/vim | 2022-04-24I have a repo where I auto-generate the SchemaStore catalog for Neovim. I use the EndBug/add-and-commit action to commit any changes. Maybe you could use a similar approach so that the wordlists in the repo are always kept up-to-date.
-
Project mention: First time using Go: Making a program to watermark photos | reddit.com/r/golang | 2022-09-14
You could improve your workflow with Goreleaser. It will build executables for different platforms via Github action and store it as asset for even easier download. (storing binary data in Git is usualy an anti-pattern). See it in Action inthis Repo of a small project of mine
-
Project mention: Automate Docker Image Builds and Push to GitHub Registry Using GitHub Actions 🐙 | dev.to | 2023-03-11
name: Docker Image Publish on: push: branches: [ "main" ] # Publish semver tags as releases. tags: [ 'v*.*.*' ] pull_request: branches: [ "main" ] env: # Use docker.io for Docker Hub if empty REGISTRY: ghcr.io # github.repository as / IMAGE_NAME: ${{ github.repository }} jobs: build: runs-on: ubuntu-latest permissions: contents: read packages: write # This is used to complete the identity challenge # with sigstore/fulcio when running outside of PRs. id-token: write steps: - name: Checkout repository uses: actions/[email protected] # Install the cosign tool except on PR # https://github.com/sigstore/cosign-installer - name: Install cosign if: github.event_name != 'pull_request' uses: sigstore/[email protected] #v2.6.0 with: cosign-release: 'v1.11.0' # Workaround: https://github.com/docker/build-push-action/issues/461 - name: Setup Docker buildx uses: docker/[email protected] # Login against a Docker registry except on PR # https://github.com/docker/login-action - name: Log into registry ${{ env.REGISTRY }} if: github.event_name != 'pull_request' uses: docker/[email protected] with: registry: ${{ env.REGISTRY }} username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} # Extract metadata (tags, labels) for Docker # https://github.com/docker/metadata-action - name: Extract Docker metadata id: meta uses: docker/[email protected] with: images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} # Build and push Docker image with Buildx (don't push on PR) # https://github.com/docker/build-push-action - name: Build and push Docker image id: build-and-push uses: docker/[email protected] with: context: "{{defaultContext}}:src" push: ${{ github.event_name != 'pull_request' }} # Don't push on PR tags: ${{ steps.meta.outputs.tags }} labels: ${{ steps.meta.outputs.labels }} cache-from: type=gha cache-to: type=gha,mode=max
-
Project mention: Automate Docker Image Builds and Push to Docker Hub Using GitHub Actions 🐳🐙 | dev.to | 2023-03-01
Set up Docker Buildx: We will use the docker/setup-buildx-action action to set up Docker Buildx.
-
Project mention: httm is for when you want to find your ZFS file snapshots really fast | reddit.com/r/zfs | 2022-04-19
Let GitHub build it for you? https://github.com/actions-rs/cargo
-
metadata-action
GitHub Action to extract metadata (tags, labels) from Git reference and GitHub events for Docker
Project mention: Automate Docker Image Builds and Push to GitHub Registry Using GitHub Actions 🐙 | dev.to | 2023-03-11name: Docker Image Publish on: push: branches: [ "main" ] # Publish semver tags as releases. tags: [ 'v*.*.*' ] pull_request: branches: [ "main" ] env: # Use docker.io for Docker Hub if empty REGISTRY: ghcr.io # github.repository as / IMAGE_NAME: ${{ github.repository }} jobs: build: runs-on: ubuntu-latest permissions: contents: read packages: write # This is used to complete the identity challenge # with sigstore/fulcio when running outside of PRs. id-token: write steps: - name: Checkout repository uses: actions/[email protected] # Install the cosign tool except on PR # https://github.com/sigstore/cosign-installer - name: Install cosign if: github.event_name != 'pull_request' uses: sigstore/[email protected] #v2.6.0 with: cosign-release: 'v1.11.0' # Workaround: https://github.com/docker/build-push-action/issues/461 - name: Setup Docker buildx uses: docker/[email protected] # Login against a Docker registry except on PR # https://github.com/docker/login-action - name: Log into registry ${{ env.REGISTRY }} if: github.event_name != 'pull_request' uses: docker/[email protected] with: registry: ${{ env.REGISTRY }} username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} # Extract metadata (tags, labels) for Docker # https://github.com/docker/metadata-action - name: Extract Docker metadata id: meta uses: docker/[email protected] with: images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }} # Build and push Docker image with Buildx (don't push on PR) # https://github.com/docker/build-push-action - name: Build and push Docker image id: build-and-push uses: docker/[email protected] with: context: "{{defaultContext}}:src" push: ${{ github.event_name != 'pull_request' }} # Don't push on PR tags: ${{ steps.meta.outputs.tags }} labels: ${{ steps.meta.outputs.labels }} cache-from: type=gha cache-to: type=gha,mode=max
-
While it is commonly associated with AWS, and their AWS IAM service, IAM is not limited to their platform. All cloud providers, such as Google Cloud and Azure DevOps, offer IAM solutions that allow users to access resources and systems. If you are looking for specific AWS IAM best practices, look no further than our AWS IAM Security Best Practices article:\ For the rest of this article, we will look at the generic best practices that have evolved over the last decade around each part of the basic question we started with, "who can access what?":
-
Sonar
Write Clean JavaScript Code. Always.. Sonar helps you commit clean code every time. With over 300 unique rules to find JavaScript bugs, code smells & vulnerabilities, Sonar finds the issues while you focus on the work.
NOTE:
The open source projects on this list are ordered by number of github stars.
The number of mentions indicates repo mentiontions in the last 12 Months or
since we started tracking (Dec 2020).
The latest post mention was on 2023-03-31.
TypeScript github-actions related posts
- Deploy Hugo to NixOS on Push to Gitea
- Where do you commit files for containers that run CI scripts?
- What are the best practices to hide sensitive information in your open source project
- How to Automatically Update Resume On Your Personal Site From OverLeaf
- A guide to using act with GitHub Actions
- [Darksouls] Remaster pour PC Controller ne fonctionne pas ?
- Automate Docker Image Builds and Push to GitHub Registry Using GitHub Actions 🐙
-
A note from our sponsor - Appwrite
appwrite.io | 31 Mar 2023
Index
What are some of the best open-source github-action projects in TypeScript? This list will help you:
| Project | Stars | |
|---|---|---|
| 1 | danger-js | 4,882 |
| 2 | actions-gh-pages | 3,776 |
| 3 | github-pages-deploy-action | 3,581 |
| 4 | build-push-action | 3,171 |
| 5 | action-gh-release | 2,514 |
| 6 | FTP-Deploy-Action | 2,463 |
| 7 | setup-php | 2,448 |
| 8 | snk | 2,151 |
| 9 | ts-nextjs-tailwind-starter | 1,741 |
| 10 | github-actions | 1,510 |
| 11 | image-actions | 1,279 |
| 12 | actions-hugo | 1,191 |
| 13 | paths-filter | 1,063 |
| 14 | actions-toolkit | 900 |
| 15 | cancel-workflow-action | 853 |
| 16 | osmosfeed | 850 |
| 17 | add-and-commit | 793 |
| 18 | goreleaser-action | 670 |
| 19 | login-action | 662 |
| 20 | setup-buildx-action | 628 |
| 21 | cargo | 584 |
| 22 | metadata-action | 579 |
| 23 | auth | 573 |
Write Clean JavaScript Code. Always.
Sonar helps you commit clean code every time. With over 300 unique rules to find JavaScript bugs, code smells & vulnerabilities, Sonar finds the issues while you focus on the work.
www.sonarsource.com