-
Updated
Sep 23, 2020
Actions
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."
Featured Actions
Getting Started
Community & Support
Taking Action With GitHub Actions
Here are 1,292 public repositories matching this topic...
-
Updated
Sep 28, 2020 - Shell
-
Updated
Sep 26, 2020 - Jupyter Notebook
-
Updated
Apr 26, 2020 - Java
-
Updated
Sep 28, 2020 - TypeScript
-
Updated
Sep 11, 2020 - TypeScript
-
Updated
Sep 24, 2020 - JavaScript
-
Updated
Sep 21, 2020 - TypeScript
-
Updated
Sep 28, 2020 - Shell
-
Updated
Sep 11, 2020 - JavaScript
-
Updated
Sep 24, 2020 - JavaScript
-
Updated
Sep 27, 2020 - Vue
-
Updated
Sep 24, 2020 - TypeScript
-
Updated
Aug 14, 2020 - TypeScript
-
Updated
Sep 23, 2020 - JavaScript
-
Updated
May 20, 2020 - Shell
-
Updated
Sep 27, 2020 - JavaScript
-
Updated
Jul 23, 2020 - Python
-
Updated
Sep 28, 2020 - CMake
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.
Possible workarounds:
- Report the size table back using a Status Check
- Not sure if GitHub's UI will handle
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']
As Queue::hasPushed(QueueableActionJob::class) wont work, it might be nice to include some assertions out of the box?
public function actionJobWasPushed(string $actionJobClass): bool
{
$this->assertTrue(Queue::getFacadeRoot() instanceof QueueFake, 'Queue was not faked. Use `Queue::fake()`.');
return collect(Queue::pushedJobs()[ActionJob::class] ?? [])
-
Updated
Sep 24, 2020 - TypeScript
-
Updated
Sep 7, 2020 - TypeScript
-
Updated
May 13, 2020 - Shell
-
Updated
Mar 15, 2018 - JavaScript
-
Updated
Sep 19, 2020 - JavaScript
Created by GitHub
Released October 16, 2018
- Organization
- actions
- Website
- github.com/features/actions
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