-
Updated
Feb 24, 2021
action
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 778 public repositories matching this topic...
-
Updated
Oct 10, 2018 - HTML
-
Updated
Feb 24, 2021 - JavaScript
-
Updated
Jun 28, 2020
-
Updated
Feb 24, 2021 - TypeScript
-
Updated
Feb 7, 2021 - Kotlin
-
Updated
Feb 4, 2021 - JavaScript
-
Updated
Dec 4, 2020
-
Updated
Feb 19, 2021 - JavaScript
-
Updated
May 8, 2019
Please include the following information:
Version of golangci-lint
- id: golangci_configuration
uses: andstor/file-existence-action@v1
with:
files: .golangci.yaml
- name: Go Lint
if: steps.golangci_configuration.outputs.files_exists == 'true'
uses: golangci/golangci-lint-action@v2
withBundle size notes
@the-dr-lazy First of all, thank you for this project, this is what I searched, but every time when I would install any dependency in the project I measure its size in bundlephobia.
redux-actions - 7kB
deox - 23kB
Is it expected to have bundle size
-
Updated
Feb 17, 2021 - Shell
-
Updated
Feb 24, 2021 - Shell
-
Updated
Apr 2, 2020 - Shell
whenever i push it repeats it. really annoying as i keep getting notifications for nothing.
-
Updated
Nov 13, 2020 - JavaScript
-
Updated
Feb 17, 2021 - Shell
-
Updated
Feb 24, 2021 - Shell
Created by GitHub
Released October 16, 2018
- Organization
- actions
- Website
- github.com/features/actions
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: