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

Fix missing scenario clone #1377

Merged
merged 1 commit into from
Mar 30, 2016
Merged

Fix missing scenario clone #1377

merged 1 commit into from
Mar 30, 2016

Conversation

thiagotalma
Copy link
Contributor

No description provided.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 90.781% when pulling c668e28 on thiagotalma:clone-fix-scenario into d13edc2 on cantino:master.

@dsander
Copy link
Collaborator

dsander commented Mar 27, 2016

Not sure if that was intensional, but I don't feel strongly about it. @cantino do you agree?

@thiagotalma Could you add a test that ensures cloned agents retain the scenarios of the original agent?

@cantino
Copy link
Member

cantino commented Mar 29, 2016

I'm not sure. @knu, was this intentional?

@knu
Copy link
Member

knu commented Mar 29, 2016

I don't know. Doesn't the clone feature predate scenarios?

@knu
Copy link
Member

knu commented Mar 29, 2016

One could easily remove preset scenarios if one wanted, so I think it'd be fine to merge this.

@cantino
Copy link
Member

cantino commented Mar 30, 2016

I'm comfortable with this. Thanks @thiagotalma!

@cantino cantino merged commit b156e52 into huginn:master Mar 30, 2016
@thiagotalma thiagotalma deleted the clone-fix-scenario branch March 30, 2016 12:56
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

5 participants