-
Updated
Jan 7, 2022
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 2,535 public repositories matching this topic...
-
Updated
Jan 8, 2022 - Shell
At the moment, it's possible to do
toc: true
to autogenerate a table of contents. I think it would be nice if there were also styling options, e.g. to have that TOC float on one side of the page.
-
Updated
Jan 10, 2022 - TypeScript
-
Updated
Jan 12, 2022 - TypeScript
-
Updated
Jan 6, 2022 - TypeScript
Is your feature request related to a problem? Please describe.
I just ran into a problem where a call to the Github API unexpectedly returned a 404 error. This failed our workflow. The error was intermittent and wasn't reproducible when I re-ran the job.
Describe the solution you'd like
I'd like any API calls made by the github client to be retried, preferably using the [retry p
-
Updated
Jan 13, 2022 - Vue
-
Updated
Oct 20, 2021 - Java
-
Updated
Dec 10, 2021 - TypeScript
-
Updated
Jan 11, 2022 - TypeScript
-
Updated
Jan 4, 2022 - JavaScript
-
Updated
Mar 3, 2021 - JavaScript
-
Updated
Jan 10, 2022 - Shell
-
Updated
Dec 26, 2021 - TypeScript
-
Updated
Jan 10, 2022 - TypeScript
-
Updated
Dec 29, 2021 - TypeScript
-
Updated
Jan 9, 2022 - JavaScript
-
Updated
Jan 8, 2022 - Shell
-
Updated
Jun 6, 2021 - Shell
-
Updated
Dec 20, 2021 - TypeScript
-
Updated
Mar 3, 2021 - JavaScript
-
Updated
Jan 9, 2022 - Go
Context
Test runner currently saves logs to the artifacts folder. (since game-ci/unity-test-runner#37) That way we can use test results reporter (which generates a html report)
Solution
Either we have to add a section to the readme, about how to run an additional action for producing the html report, or we should integrate the reporter in this action and s
-
Updated
Dec 6, 2021 - TypeScript
This issue relates to the func-style rule.
During the transition from TSLint (now deprecated) to ESLint for typescript linting we introduced some new rules that don't yet pass and added a temporary override in the .eslintrc.json file to temporarily disable them.
This issue covers removing that temporary override and any changes to the typescript
Created by GitHub
Released October 16, 2018
- Organization
- actions
- Website
- github.com/features/actions
Describe the bug
git diff-treeused by linter onpushchecks only files from the last commit and regardless of files status, so deleted or renamed files are also checked.There are now 2 different
gitcommands used for finding the list of broken files (find them here: https://github.com/github/super-linter/blob/v3.14.4/lib/functions/buildFileList.sh#L59-L105).git diff-treeis u