Writing a good condition in GitHub workflowsConditions are used to control job or step execution and are defined by if YAML key like this: jobs: first-job: if: ${{ github.event_name == 'workflow_dispatch' }} #<---- conditions runs-on: ubuntu-latest steps: - name: Checkout ...Mar 4, 2025 · 3 min readjurajsim.hashnode.dev
A Comparison of Calling vs. Dispatching Workflows in GitHub ActionsThere are two types of execution units in GitHub Actions. One is called a workflow, which organizes global pipeline execution into smaller units like jobs and steps. The second one is called a custom/composed action, and it can represent one (or mult...Feb 18, 2025 · 9 min readjurajsim.hashnode.dev
Sending data between GitHub workflowsIn my last article, How to Send More Than Ten Inputs with Workflow Dispatch, I described how to get around that ten inputs limit with an extended JavaScript action.However all inputs size combined is also limited to max. 65 kbytes in total: The max...Dec 23, 2024 · 6 min readjurajsim.hashnode.dev
How to Send More Than Ten Inputs with Workflow DispatchThere is a limit of ten inputs on the number of inputs you can send when dispatching a GitHub workflow. The maximum number of top-level properties for inputs is 10. However, with highly parameterized workflows, I quickly hit the limit. In my case...Dec 6, 2024 · 7 min readjurajsim.hashnode.dev
How to connect dispatching and dispatched workflowsIn the last article in this series I mentioned that by switching from reusable workflows to dispatching we can lost some navigation clarity. Dispatched workflow has no connection about its dispatcher, so it might be difficult to search what dispatche...Nov 8, 2024 · 10 min readjurajsim.hashnode.dev