Releases: boasiHQ/interactive-inputs
v2.4.0 - Release Notes
What's Changed
- Updated the Slack notifier to ensure that all messages are not unfurled, providing users with clear and less convoluted messages.
[II-X] Added behaviour to not UnfurlMedia and not UnfurlLinks by default by @mnarozny in #18
*=*=*=*=*=*=*=*=*=*=*=*=*
We recommend using the reference boasihq/interactive-inputs@v2
in your workflows to ensure you are getting the latest features of this action.
*=*=*=*=*=*=*=*=*=*=*=*=*
Screenshots
- Before:
- After
Notes
Thank you, @mnarozny, for this contribution! I'm sure many will enjoy the simplified messaging.
Also, thank you all for your feedback and feature suggestions (which are tracked here)! Please continue to let us know what features you'd like to see next.
v2.3.0 - Release Notes
What's Changed
- Added support for
file
andmultifile
input types, which gives users the ability to upload files to their workflow during runtime- Users can lock down the type of files allowed to upload on both
file
andmultifile
input types by using unique file type specifiers with theacceptedFileTypes
field property
- Users can lock down the type of files allowed to upload on both
- Update logic to make sure the user cannot provide the same input field label multiple times
- Updated README to improve readability
Full Changelog: v2.2.0...v2.3.0
Screenshots
Notes
Thank you for your feedback and feature suggestions! Please continue to let us know what features you'd like to see next.
v2.2.0 - Release Notes
What's Changed
- Added support for sending messages to message threads on Slack and Discord
- Updated action to limit the amount of text in a typical message's boilerplate template, ensuring that crucial information is hyperlinked. The general structure of the boilerplate is:
- Title (If provided when adding action to workflow(s))
- Link to run using action (always)
- Initiator (Github actor handle, always)
- Message
- Updated runner to show a more human-readable error when timed out
- Update message for when the server has started to use respective platform syntax
[II-I3] Improve message formatting and introduce thread messaging support by @ooaklee in #4
Full Changelog: v2.1.0...v2.2.0
Screenshots
Notes
Thank you for your feedback and feature suggestions! Please continue to let us know what features you'd like to see next.
v2.1.0 - Release Notes
Changlelog
- Added feature to make the selection for
select
/multiselect
field types automatically copy to clipboard (More details: #1) - Users can now use the field property
disableAutoCopySelection
(defaults tofalse
) to stop the copy of their selected choice to their clipboard - Updated the README with the new changes regarding field types
select
andmultiselect
.
Notes
Thank you for your feedback and feature suggestions! Please continue to let us know what features you'd like to see next.
v2.0.0 - Release Notes
Changlelog
- Added support for sending notifications to Slack (via Slack bot) and Discord (via webhooks). Click here for instructions on setting it up.
Instructions on enabling notifiers can be found in the README
- Update action to expect Ngrok auth token as an
input
rather than an environment variable - Fixed bug that stopped exit code making it to the top of the action
- Added source code to repo
Notes
Thank you for your feedback and feature suggestions! Please continue to let us know what features you'd like to see next.
v1.0.0 - Release Notes
Changelog
- The action automatically creates output names based on the label provided by the user when declaring the input fields.
...
- name: Example Interactive Inputs Step
id: interactive-inputs
uses: boasihq/interactive-inputs@v1
with:
...
interactive: |
fields:
- label: continue-roll-out
properties:
display: Continue to roll out?
...
The output for the example above will be
${{ steps.interactive-inputs.outputs.continue-roll-out }}
- Support for the following input field types has been added:
text
textarea
number
select
multiselect
boolean
- Each input field type has additional properties that can be added by the user
- Users can create an Interactive Input portal if they provide an
NGROK_AUTHTOKEN
that the action can use. - Users have the ability to arrange the fields in the portal in the order they add the fields when incorporating actions into their workflow.
More information on how to fully utilise the action can be found in the README