-
-
Notifications
You must be signed in to change notification settings - Fork 739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trigger name collision workaround #5335
Conversation
…ame collisions noted in issue StackStorm#4641.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This looks like a good clean change. @mjtice would you please sign the CLA #5335 (comment) ? It would be great to merge this sooner rather than later. |
Done. |
It looks like maintainer edits aren't allowed - and I don't think github allows that for forks in organizations. So, let's see if we can get this ready to merge together. Please:
I'm not sure why GHA tests haven't run for the last commit (only circleci ran? weird). I hope tests will run once you do that, if not I might need to pull in your commits another way. |
I just opened #5383 to include your changes. As soon as someone else approves it, we can get it merged. |
This addresses the jinja trigger name collision noted in issue #4641