docker_images
action-tmate
| docker_images | action-tmate | |
|---|---|---|
| 1 | 13 | |
| 177 | 2,652 | |
| - | - | |
| 7.2 | 5.5 | |
| about 2 months ago | 16 days ago | |
| Shell | JavaScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker_images
action-tmate
-
How to debug GitHub actions. Real-world example
The go-to method of debugging GitHub Actions is tmate. With tmate we can connect to our running Action terminal and see what is going on there by executing some simple commands!
-
GitHub Actions Are a Problem
In addition to the suggestions others have made for locally testing workflows, there are also reverse shell actions[0] that can be used for troubleshooting CI failures on the GH runners themselves.
[0] https://github.com/mxschmitt/action-tmate
-
GitHub Actions could be so much better
Been through that git commit; git push; repeat cycle too much as well until i discovered https://github.com/mxschmitt/action-tmate which gives a shell in between steps, which does not help with all problems but sure it's makes it less painful at times.
- How do you debug CI/CD pipelines? Breakpoints?
-
How easy is it to troubleshoot GHA workflows?
In addition to everything here, I also will set up https://github.com/mxschmitt/action-tmate when Iām debugging. It helps tremendously since you can temporarily access the server.
-
Act: Run your GitHub Actions locally
Unfortunately act is only capable of running very simple workflows. I've found this action to be more useful against the endless PR stream: https://github.com/mxschmitt/action-tmate
You drop it in your workflow and get an SSH shell into the worker, figure things out iteratively, then push when it's working.
-
CI/CD using GitHub Actions for Rails and Docker
Solution: Tip o' the hat to Daniela Baron here, there's a real life saver of tool call tmate.
-
Hosting VMs on GitHub Actions?
Here's a recent case where users of tmate - which lets you SSH into an actions worker - reported problems: https://github.com/mxschmitt/action-tmate/issues/104
-
Github actions error while pushing code to package registry
see: https://github.com/mxschmitt/action-tmate
-
Work with GitHub Actions in Your Terminal with GitHub CLI
Thought I'd get their docs updated - https://github.com/mxschmitt/action-tmate#manually-triggered...
What are some alternatives?
runner - The Runner for GitHub Actions :rocket:
reverse-rdp-windows-github-actions - Reverse Remote Desktop into Windows on GitHub Actions for Debugging and/or Job Introspection [GET https://api.github.com/repos/nelsonjchen/reverse-rdp-windows-github-actions: 403 - Repository access blocked]
batect - (NOT MAINTAINED) Build And Testing Environments as Code Tool
act - Run your GitHub Actions locally š
djinn - Source code for the Djinn CI platform
floatly - An extension that adds a floating button for browser quick actions
mongodb-github-action - Use MongoDB in GitHub Actions
act-environments
github-activity-readme - Updates README with the recent GitHub activity of a user
docker-flask-example - A production ready example Flask app that's using Docker and Docker Compose.
ssh-agent - GitHub Action to setup `ssh-agent` with a private key