github-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 5,811 public repositories matching this topic...
-
Updated
Aug 26, 2021
-
Updated
Aug 26, 2021 - Shell
-
Updated
Aug 28, 2021 - Shell
-
Updated
Aug 24, 2021 - Python
-
Updated
Aug 25, 2021 - TypeScript
-
Updated
Aug 27, 2021 - TypeScript
-
Updated
Aug 28, 2021 - TypeScript
-
Updated
Aug 24, 2021 - TypeScript
-
Updated
May 15, 2021 - Dockerfile
-
Updated
Aug 15, 2021 - Python
-
Updated
Aug 28, 2021 - Jupyter Notebook
-
Updated
Aug 25, 2021 - JavaScript
⚠️ Is your feature request related to a problem? Please describe
Add support for code coverage
💡 Describe the solution you'd like
Ideally we could setup jacoco + codecov to have an automated test report after every push/pr.
🤚 Do you want to develop this feature yourself?
- Yes
- No
This feature is up for grab
-
Updated
Aug 28, 2021 - Rust
-
Updated
Mar 3, 2021 - JavaScript
-
Updated
Aug 11, 2021 - JavaScript
-
Updated
Aug 27, 2021 - Go
-
Updated
Aug 15, 2021 - TypeScript

-
Updated
Aug 11, 2021 - TypeScript
-
Updated
Aug 13, 2021 - TypeScript
-
Updated
Aug 20, 2021 - CMake
-
Updated
Aug 10, 2021 - TypeScript
-
Updated
Aug 28, 2021 - Python
-
Updated
Aug 28, 2021 - Python
-
Updated
Jul 19, 2021 - JavaScript
-
Updated
Aug 25, 2021 - TypeScript
-
Updated
Aug 5, 2021 - TypeScript
Created by GitHub
Released October 16, 2018
- Organization
- actions
- Website
- github.com/features/actions
Would be faster if we can reuse the already downloaded one, this is specially good for not cloud runners.
We should download the wrapped runner once (GH or GL), install it in the system and make
cml-runner
to use it always.If we are changing the SCM we should download the other wrapped runner.