Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| GitHub Actions on g1t, part one: reading workflows | 1 | //! GitHub Actions on g1t. A repository's `.github/workflows/*.yml` run on |
| 2 | //! g1t as they are: this crate reads them ([`workflow`]), evaluates their | |
| 3 | //! `${{ }}` expressions ([`expr`]), matches their branch and path filters | |
| 4 | //! ([`filter`]), expands their matrices ([`matrix`]), and says which g1t | |
| 5 | //! events are which GitHub events ([`events`]). | |
| 6 | //! | |
| 7 | //! It has no I/O, so the actions service (in a Worker) and the sandbox | |
| 8 | //! (in a container) share it: the service decides what runs, the sandbox | |
| 9 | //! runs the steps, and both read workflows and expressions the same way. | |
| 10 | ||
| 11 | pub mod events; | |
| 12 | pub mod expr; | |
| 13 | pub mod filter; | |
| 14 | pub mod matrix; | |
| 15 | pub mod workflow; |