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,177 public repositories matching this topic...
-
Updated
Jan 7, 2022
-
Updated
Jan 8, 2022 - Go
-
Updated
Jan 8, 2022 - Shell
-
Updated
Jan 8, 2022 - Shell
-
Updated
Dec 28, 2021 - TypeScript
-
Updated
Jan 8, 2022 - TypeScript
-
Updated
Jan 9, 2022 - Python
jest.it.each reduces the boilerplate test code and improves the readability and maintainability.
Currently config, tools and coverage tests use jest.it.each. The same can be done for utils, extensions and install tests.
Ref:
-
Updated
Jan 6, 2022 - TypeScript
-
Updated
May 15, 2021 - Dockerfile
-
Updated
Dec 19, 2021 - JavaScript
-
Updated
Jan 5, 2022 - Python
-
Updated
Jan 8, 2022 - SCSS
-
Updated
Jan 9, 2022 - Jupyter Notebook
-
Updated
Dec 10, 2021 - 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
Jan 7, 2022 - Rust
⚠️ 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
Jan 5, 2022 - TypeScript
-
Updated
Jan 4, 2022 - JavaScript
-
Updated
Jan 6, 2022
-
Updated
Jan 8, 2022 - TypeScript
Error photo
https://github.com/NhanAZ/Images/blob/master/errordisplayimage.jpg
Device info I use
Android 11; Redmi Note 8 Build/RKQ1.201004.002
The web version I use
Chrome 96.0.4664.92
Github profile in the picture
-
Updated
Dec 2, 2021 - TypeScript
-
Updated
Mar 3, 2021 - JavaScript
-
Updated
Jan 9, 2022 - Shell
-
Updated
Jan 8, 2022 - Python
-
Updated
Oct 7, 2021 - CMake
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