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 7,742 public repositories matching this topic...
-
Updated
Jan 24, 2022
-
Updated
Feb 27, 2022 - Go
-
Updated
Feb 23, 2022 - Shell
-
Updated
Feb 10, 2022 - Shell
-
Updated
Feb 27, 2022 - TypeScript
-
Updated
Feb 27, 2022 - TypeScript
-
Updated
Feb 13, 2022 - TypeScript
-
Updated
Feb 26, 2022 - TypeScript
-
Updated
Feb 6, 2022 - Dockerfile
-
Updated
Feb 23, 2022 - JavaScript
-
Updated
Feb 8, 2022 - Python
-
Updated
Feb 21, 2022 - HTML
-
Updated
Feb 19, 2022 - TypeScript
I wanted to use topology spread constraints to control how Pods are spread across in my cluster by topologySpreadConstraints
section in runner deployment. But i faced to following error: `error validating data: ValidationError(RunnerDeployment.spec.template.spec): unknown field "topologySpreadConstraints" in dev.summerwind.actions.v1alpha1.RunnerDeployment.spec.template.spec; if you choose to ig
-
Updated
Feb 27, 2022 - Jupyter Notebook
-
Updated
Feb 20, 2022
-
Updated
Feb 24, 2022 - Rust

-
Updated
Feb 17, 2022 - TypeScript
Error description photo
Device used in the photo
Android 11; Redmi Note 8 Build/RKQ1.201004.002
Browser version used in the photo
Chrome 96.0.4664.92
⚠️ 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
Feb 13, 2022 - JavaScript
-
Updated
Feb 21, 2022 - TypeScript
-
Updated
Feb 13, 2022 - Shell
-
Updated
Feb 21, 2022 - TypeScript
-
Updated
Mar 3, 2021 - JavaScript
-
Updated
Feb 27, 2022 - Python
-
Updated
Jan 22, 2022 - CMake
-
Updated
Feb 26, 2022 - JavaScript
Created by GitHub
Released October 16, 2018
- Organization
- actions
- Website
- github.com/features/actions
I noticed that when CML produces the reports (as per in
cml-send-comment --update --pr report.md
) such reports are shown in the PR conversation as belonging to a certain user rather than GitHub actions reports. Is this intended behaviour or is there a setting/flag where we can choose which user to assign to the comments reports?I haven't figured out how such user is chosen, I suspect it is t