Interactiveinputs
interactiveinputs.com
Dynamic runtime inputs ❤️ GitHub Actions | Interactive Inputs
The most effective way for integrating runtime inputs into your GitHub Action Workflows and Actions
GitHub
docs.github.com › actions › using-workflows › workflow-syntax-for-github-actions
Workflow syntax for GitHub Actions - GitHub Docs
GitHub displays the workflow run ... "Actions" tab. If run-name is omitted or is only whitespace, then the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a push or pull_request event, it is set as the commit message or the title of the pull request. This value can include expressions and can reference the github and inputs ...
yaml - How to define inputs in a `push` trigger in Github Actions? - Stack Overflow
I want to have input variables defined in the inputs section of the push event. I get this error via my ID: Property inputs is not allowed.yaml-schema: GitHub Workflow And the variable is not passed More on stackoverflow.com
Using github.inputs and variables in workflows - Stack Overflow
So basically what I try to do is as following if there is a push to repository A trigger the pipeline of repository B with an input thatis the the name of the branch in repository A that is pushed ... More on stackoverflow.com
GitHub Actions: How to view inputs for workflow_dispatch? - Stack Overflow
My idea here is to write my inputs from workflow_dispatch on each pipeline run. . For example, in Bitbucket pipelines input parameters shown after custom - Is there a way to do something similar for More on stackoverflow.com
Support list input type
If you are having an issue or question about GitHub Actions then please contact customer support · If your issue is relevant to this repository, please include the information below: Describe the enhancement An action should be able to have an input type which is a list of strings. More on github.com
Videos
Add Inputs to GitHub Actions Workflows - GitHub Actions Tutorial
19:15
GitHub Actions - Run workflows manually with inputs - YouTube
Variables, Secrets and Inputs in Github Actions | Github ...
01:01
Freeform Input In GitHub Actions Workflow #githubactions #github ...
GitHub Actions Tutorial: Using Variables ,Secrets and Inputs in ...
GitHub
github.blog › home › changelogs › github actions: input types for manual workflows
GitHub Actions: Input types for manual workflows - GitHub Changelog
March 22, 2025 - name: Mixed inputs on: workflow_dispatch: inputs: name: type: choice description: Who to greet options: - monalisa - cschleiden message: required: true use-emoji: type: boolean description: Include 🎉🤣 emojis environment: type: environment jobs: greet: runs-on: ubuntu-latest steps: - name: Send greeting run: echo "${{ github.event.inputs.message }} ${{ fromJSON('["", "🥳"]')[github.event.inputs.use-emoji == 'true'] }} ${{ github.event.inputs.name }}"
Stack Overflow
stackoverflow.com › questions › 76211346 › how-to-define-inputs-in-a-push-trigger-in-github-actions
yaml - How to define inputs in a `push` trigger in Github Actions? - Stack Overflow
name: Main on: push: branches: - main - <other branch> inputs: database_version: type: string required: true default: abcd ... This is the doc about Metadata syntax for Github Action.
GitHub
docs.github.com › en › actions › reference › workflows-and-actions › contexts
Contexts reference - GitHub Docs
The inputs context contains input properties passed to an action, to a reusable workflow, or to a manually triggered workflow.
GitHub
github.com › marketplace › actions › interactive-inputs-action
Interactive Inputs Action - GitHub Marketplace
name: Interactive Inputs on: [push] jobs: get-choice: runs-on: ubuntu-latest steps: - name: Test interactive inputs action id: interactive-inputs-action uses: NivEz/interactive-inputs-action@v1 # You can use a different version / tag @vx.x.x with: telegram-api-token: ${{ secrets.TELEGRAM_API_TOKEN }} telegram-chat-id: ${{ secrets.CHAT_ID }} question: How are you today?
Claude
code.claude.com › docs › en › github-actions
Claude Code GitHub Actions - Claude Code Docs
If you’re currently using the beta version of Claude Code GitHub Actions, we recommend that you update your workflows to use the GA version. The new version simplifies configuration while adding powerful new features like automatic mode detection. All beta users must make these changes to their workflow files in order to upgrade: Update the action version: Change @beta to @v1 · Remove mode configuration: Delete mode: "tag" or mode: "agent" (now auto-detected) Update prompt inputs: Replace direct_prompt with prompt ·
GitHub
docs.github.com › en › enterprise-cloud@latest › graphql › reference › input-objects
Input objects - GitHub Enterprise Cloud Docs
Autogenerated input type of ChangeUserStatus. Information from a check run analysis to specific lines of code. Information from a check run analysis to specific lines of code. Possible further actions the integrator can perform. The filters that are available when fetching check runs. Descriptive details about the check run. Images attached to the check run output displayed in the GitHub pull request UI.
Stack Overflow
stackoverflow.com › questions › 74437885 › using-github-inputs-and-variables-in-workflows
Using github.inputs and variables in workflows - Stack Overflow
23 GitHub Actions: pass data from workflow to another workflow? 58 Dropdown for GitHub Workflows input parameters · 12 Combine dynamic Github Workflow matrix with input values and predefined values · 7 Github action how to access the inputs · 12 GitHub Action workflow_call does not use up to date input values ·
YouTube
youtube.com › mixible
Schedule Trigger Github Action workflow with Input parameters - YouTube
Welcome to Mixible, your go-to source for comprehensive and informative content covering a broad range of topics from Stack Exchange websites. Our channel is...
Published August 26, 2023 Views 23
Daily.dev
app.daily.dev › home › playful programming › manually trigger a github action with workflow_dispatch
Manually Trigger a GitHub Action with workflow_dispatch | daily.dev
March 17, 2026 - A guide to using `workflow_dispatch` in GitHub Actions to manually trigger workflows without a push or pull request. Covers basic setup, passing custom input parameters, supported input types (string, boolean, choice), required fields, and accessing inputs via `github.event.inputs` in workflow steps.
OneUptime
oneuptime.com › home › blog › how to use workflow dispatch inputs in github actions
How to Use Workflow Dispatch Inputs in GitHub Actions
December 20, 2025 - name: Production Deploy on: workflow_dispatch: inputs: version: description: 'Version to deploy (e.g., v1.2.3 or commit SHA)' required: true type: string environment: description: 'Target environment' required: true type: environment skip_tests: description: 'Skip test execution' type: boolean default: false rollback_on_failure: description: 'Automatically rollback on failure' type: boolean default: true notify_channels: description: 'Notification channels' type: choice options: - slack-only - email-only - both - none default: 'slack-only' jobs: validate: runs-on: ubuntu-latest outputs: resolv
GitHub
github.com › orgs › community › discussions › 11795
workflow_dispach to have dynamic inputs parameters · community · Discussion #11795
It'd be good to have dynamic input ... one form input to the operator. For example, on select choices <stg, prod>, we can hide/show/change the other options, before the operator clicks the Run Workflow. Beta Was this translation helpful? Give feedback. ... There was an error while loading. Please reload this page. Something went wrong. There was an error while loading. Please reload this page. ... Yes, GitHub action inputs really ...
GitHub
docs.github.com › en › actions › reference › workflows-and-actions › metadata-syntax
Metadata syntax reference - GitHub Actions
When you specify an input, GitHub creates an environment variable for the input with the name INPUT_<VARIABLE_NAME>. The environment variable created converts input names to uppercase letters and replaces spaces with _ characters. If the action is written using a composite, then it will not automatically get INPUT_<VARIABLE_NAME>. With composite actions you can use inputs Contexts reference to access action inputs.
GitHub
docs.github.com › en › actions
GitHub Actions documentation - GitHub Docs
You can discover, create, and share actions to perform any job you'd like, including CI/CD, and combine actions in a completely customized workflow. ... Try out the core features of GitHub Actions in minutes.
Top answer 1 of 6
26
You can use the run-name parameter to change the name of the run in the actions list:
Example of
run-namerun-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
Be aware that, if you are using Github Enterprise server, this parameter was introduced in version 3.8.
2 of 6
24
Although this does not directly answer your question, I'm adding it here because this is where I landed looking for the answer on how to output all my workflow inputs.
In my case I am using a workflow_dispatch trigger - YMMV if you are using a different trigger, but I suspect it would work the same way.
As with the other answer proposed, you will need to do this as a step within your job:
on:
workflow_dispatch:
inputs:
myInput:
default: "my input value"
jobs:
myJob:
steps:
- name: Output Inputs
run: echo "${{ toJSON(github.event.inputs) }}"
This will result in output you can view in your GitHub action execution output with the inputs serialized as JSON:
{
"myInput": "my input value"
}
GitHub
github.com › actions › toolkit › issues › 184
Support list input type · Issue #184 · actions/toolkit
October 10, 2019 - If you are having an issue or question ... Describe the enhancement An action should be able to have an input type which is a list of strings....
Author bryanmacfarlane