jupyterhub/action-k8s-await-workloads#
A Github Action to await k8s workloads to become Ready
tooling · owned by JupyterHub and Binder · on GitHub · scanned at commit f2f60c4
Reach#
Packages: none
Container images: none
Run by other repositories: 4 in their CI
Live service: none
Security boundary: no
Why these labels: The repository defines a GitHub Action (action.yaml, README: ‘GitHub Action: Await k8s workloads’) designed to run in CI workflows of other projects. (deepseek-v4-pro)
Security topics#
zizmor: missing. No sign of zizmor.
SECURITY.md: n/a. Ships no package or image.
PyPI attestations: n/a. No PyPI package.
npm trusted publishing: n/a. No npm package.
Supported Python: n/a. No PyPI package.
Owner: done. Owned by JupyterHub and Binder.
CI and releases#
Workflows: 4, run on pull_request, push, release, workflow_dispatch
Publishes: cloud
Secrets: none
Actions: 8, 1 by commit, 7 by tag. Third-party, not pinned: peter-evans/create-pull-request@v8
Build requirements: none
Details#
Run it in their CI: binder-examples/zero-to-jupyterhub-k8s, jupyterhub/binderhub, jupyterhub/pebble-helm-chart, jupyterhub/zero-to-jupyterhub-k8s
All actions it uses: Actions-R-Us/actions-tagger@330ddfa, actions/checkout@v6, actions/setup-node@v6, actions/setup-python@v6, jupyterhub/action-k3s-helm@v4, jupyterhub/action-k8s-await-workloads@v3, jupyterhub/action-k8s-namespace-report@v1, peter-evans/create-pull-request@v8
Files: 38: 16 config, 11 code, 6 other, 5 docs