A curated list of awesome actions to use on GitHub
-
Updated
Nov 18, 2020
{{ message }}
GitHub Actions gives you the flexibility to build an automated software development lifecycle workflow. You can write individual tasks, called actions, and combine them to create a custom workflow. Workflows are custom automated processes that you can set up in your repository to build, test, package, release, or deploy any code project on GitHub.
“With GitHub Actions you can build end-to-end continuous integration (CI) and continuous deployment (CD) capabilities directly in your repository. GitHub Actions powers GitHub's built-in continuous integration service. For more information, see "About continuous integration."
Taking Action With GitHub Actions
A curated list of awesome actions to use on GitHub
An easy to use blogging platform, with enhanced support for Jupyter Notebooks.
The free Zapier/IFTTT alternative for developers to automate your workflows based on Github actions
It's a material-design about screen to use on your Android apps. A developer profile and application information easy to integrate.
GitHub Actions for GitHub Pages
An Action to create releases via the GitHub Release API
Write workflows scripting the GitHub API in JavaScript
Debug your GitHub Actions via SSH by using tmate to get access to the runner system itself.
A Github Action used to build and publish Docker images
GitHub Action that uploads coverage to Codecov
Flutter environment for use in actions. It works on Linux, Windows, and macOS.
GitHub Actions for Hugo
An Action to upload a release asset via the GitHub Release API
GitHub Action for running Cypress end-to-end tests
Framework for Building Virtual Assistants with Dialogflow and python
Brett Fox's answer to When VCs say the giants will enter the market and put you out of business in a day, what is the best answer you can give? - Quora
July 19, 2019 at 01:27PM
via Instapaper https://ift.tt/32B5pTS
Boiler plate template for C++ projects, with CMake, Doctest, Travis CI, Appveyor, Github Actions and coverage reports.
Currently certain PR's coming from forks result in the action running in the context of the fork, which means it can't post a comment or a PR review to the PR/issue.
Only a subset of the inputs documented are actually allowed in the action.yml, resulting in the following warning when I use customParameters, versioning, and other parameters:
##[warning]Unexpected input 'customParameters', valid inputs are ['unityVersion', 'targetPlatform', 'projectPath', 'buildName', 'buildsPath', 'buildMethod']
I am not sure if this belongs here, but I am having an issue when using this Github Action.
This is the link to the github run that failed:
https://github.com/jampp/migratron/pull/25/checks?check_run_id=456554120
and the content is:
Uploading distributions to https://test.pypi.org/legacy/
Uploading migratron-1.1.0-py3-none-any.whl
0%| | 0.00/30.5k [00:00<?, ?B/s]
100%|
GitHub Action for GoReleaser
An action to download a prebuilt Ruby and add it to the PATH in 5 seconds
Created by GitHub
Released October 16, 2018
Is your feature request related to a problem? Please describe.
Following the guidance of github, many developers are moving to
mainas their default branch. Saving developers from the very small hindrance of usingDEFAULT_BRANCH: mainwould contribute to smoothing the transition.Describe the solution you'd like
The default branch should be
main. If it does not exist, use `m