-
Updated
Sep 18, 2020 - Go
workflows
Here are 285 public repositories matching this topic...
-
Updated
Sep 18, 2020 - Ruby
-
Updated
Aug 20, 2020 - Python
-
Updated
Aug 23, 2020 - Python
-
Updated
Aug 29, 2020 - Python
-
Updated
Sep 18, 2020 - JavaScript
The existing HTTP Request Trigger activity needs to be enhanced so that it allows users to have it generate a SAS token. The workflow will then only be triggered if the provided SAS token is valid. This prevents the workflow from being invoked by anyone other than those who have the full URL (including the SAS token appended as a querystring).
-
Updated
Feb 3, 2020 - Python
-
Updated
Dec 16, 2018 - Rust
Is your feature request related to a problem? Please describe.
cloneDirectory needs to be specified like https://github.com/argoproj/argo-events/blob/master/examples/sensors/trigger-source-git.yaml#L34, otherwise it will error out.
Describe the solution you'd like
If cloneDirectory is missing, use a temp dir to do it.
Describe alternatives you've considered
A clear and con
-
Updated
Sep 18, 2020 - Go
-
Updated
Jul 22, 2019 - Dockerfile
-
Updated
Aug 21, 2020 - PHP
Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).
To Reproduce
odin deploy -f test.job.yamlodin log -i {job_id}
vagrant@vagrant:~/odin$ odin log -i dea194794589
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x79c764]
goroutine
I am not sure if this belongs here, but I am having an issue when using this Github Action.
This is the link to the github run that failed:
https://github.com/jampp/migratron/pull/25/checks?check_run_id=456554120
and the content is:
Uploading distributions to https://test.pypi.org/legacy/
Uploading migratron-1.1.0-py3-none-any.whl
0%| | 0.00/30.5k [00:00<?, ?B/s]
100%|
Inspired by common-workflow-language/common-workflow-language#125 (comment)
And if not, do we want it to?
We can add the --skip-pull, --substitution, --config, etc. flags to popper sh to enhance usability.
-
Updated
Sep 13, 2020 - TypeScript
-
Updated
Sep 16, 2020 - JavaScript
-
Updated
Sep 18, 2020 - Go
-
Updated
Jan 2, 2020 - C#
-
Updated
May 1, 2019 - Go
-
Updated
Sep 16, 2020 - C#
-
Updated
Jul 1, 2020 - Java
Improve this page
Add a description, image, and links to the workflows topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the workflows topic, visit your repo's landing page and select "manage topics."
An addition to Add python warning if install a pack that only supports python 2 #5037 PR and Python 2 Deprecation Game Plan, apart of warning for
pack install, we might need to also warn users that's running StackStorm in py2 environment.I'd suggest to show and log that warning for each st2