Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/austenstone/actions-playground

Playground for actions
https://github.com/austenstone/actions-playground

actions github github-actions

Last synced: 20 days ago
JSON representation

Playground for actions

Awesome Lists containing this project

README 

        
GitHub Actions makes automation easy!



Improve the quality of your code and make your life more productive through devops!



# [GitHub Actions](https://docs.github.com/en/actions)



Automate, customize, and execute your software development workflows right in your repository with GitHub Actions. You can discover, create, and share actions to perform any job you'd like, including CI/CD, and combine actions in a completely customized workflow.



## [Actions Workflows](https://docs.github.com/en/actions/using-workflows)



A workflow is a configurable automated process that will run one or more jobs. Each job is it's ow





  




### [Events that trigger workflows](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows)



You can configure your workflows to run when specific activity on GitHub happens, at a scheduled time, or when an event outside of GitHub occurs.



# [Actions](https://docs.github.com/en/actions/learn-github-actions/finding-and-customizing-actions)



Actions are the building blocks that power your workflow. A workflow can contain actions created by the community, or you can create your own actions directly within your application's repository. This guide will show you how to discover, use, and customize actions.



### [Actions Marketplace](https://github.com/marketplace?type=actions)




The GitHub Marketplace is a place where you can share your apps and actions publicly with all GitHub users.



Anyone can publish an action in GitHub Marketplace. GitHub verifies some partner organizations and these are shown as verified creators.



## [Status Checks](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)



Status checks let you know if your commits meet the conditions set for the repository you're contributing to.



If status checks are required for a repository, the required status checks must pass before you can merge your branch into the protected branch. For more information, see "[About protected branches](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)."



![image](https://user-images.githubusercontent.com/22425467/186950765-13694463-d883-4661-a9ae-87098009e302.png)



## [Environments](https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment)

Environments are used to describe a general deployment target like `production`, `staging`, or `development`.



You can configure environments with protection rules and secrets. A workflow job that references an environment must follow any protection rules for the environment before running or accessing the environment's secrets.



## Resources

- [Sales Page](https://github.com/features/actions)

- [Pricing Details](https://github.com/features/actions#pricing-details)