The Runner Container Hooks repo provides a set of packages that implement the container hooks feature in the actions/runner. These can be used as is, or you can use them as a guide to implement your own hooks.
More information on how to implement your own hooks can be found in the adr. The examples folder provides example inputs for each hook.
Thank you for your interest in this GitHub action, however, right now we are not taking contributions.
We continue to focus our resources on strategic areas that help our customers be successful while making developers' lives easier. While GitHub Actions remains a key part of this vision, we are allocating resources towards other areas of Actions and are not taking contributions to this repository at this time. The GitHub public roadmap is the best place to follow along for any updates on features we’re working on and what stage they’re in.
We are taking the following steps to better direct requests related to GitHub Actions, including:
-
We will be directing questions and support requests to our Community Discussions area
-
High Priority bugs can be reported through Community Discussions or you can report these to our support team https://support.github.com/contact/bug-report.
-
Security Issues should be handled as per our security.md
We will still provide security updates for this project and fix major breaking changes during this time.
You are welcome to still raise bugs in this repo.
Three projects are included in the packages folder
- k8s: A kubernetes hook implementation that spins up pods dynamically to run a job. More details can be found in the readme
- docker: A hook implementation of the runner's docker implementation. More details can be found in the readme
- hooklib: a shared library which contains typescript definitions and utilities that the other projects consume
This project is licensed under the terms of the MIT open source license. Please refer to MIT for the full terms.
See the Codeowners
Find a bug? Please file an issue in this repository using the issue templates.
See our Code of Conduct