Skip to content
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

Feature activity #4

Merged
merged 30 commits into from
Nov 2, 2018
Merged

Feature activity #4

merged 30 commits into from
Nov 2, 2018

Conversation

pointlander
Copy link
Contributor

No description provided.

@fm-tibco
Copy link

fm-tibco commented Nov 1, 2018

@mellistibco should we consider moving the goja activity to the core contrib or its own repo? Seems like it can be useful to the other actions.

@mellistibco
Copy link
Member

👍 @fm-tibco. I think the js activity should probably be a standalone repo. Seems like a useful thing someone would want to leverage regardless of the action...

@mellistibco
Copy link
Member

@pointlander can we pull out the js execute activity and place it into its own repo? What do you think the repo should be named?

@pointlander
Copy link
Contributor Author

@mellistibco The javascript activity can be in a repo named js-activity or javascript-activity.

@mellistibco
Copy link
Member

@pointlander I created a jsexec repo.

@fm-tibco
Copy link

fm-tibco commented Nov 1, 2018

I think I prefer js-activity as the repo... thoughts? Btw, @mellistibco did you review the PR?

@pointlander pointlander merged commit f6fff27 into master Nov 2, 2018
@pointlander pointlander deleted the feature-activity branch June 13, 2019 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants