Conversation
…tions-for-sending-messages' of github.com:HyperAgents/ns.hyperagents.org into 227-motivating-scenario-discovery-of-behavior-specifications-for-sending-messages
…ior-specifications/README.md to domains/manufacturing-environments/discover-messaging-behavior-specificationsREADME.md
…-specificationsREADME.md to domains/manufacturing-environments/discover-messaging-behavior-specifications/README.md
…tions-for-sending-messages' of github.com:HyperAgents/ns.hyperagents.org into 227-motivating-scenario-discovery-of-behavior-specifications-for-sending-messages
danaivach
requested review from
NicoRobertIn,
andreiciortea and
maximelefrancois86
NicoRobertIn
left a comment
NicoRobertIn
left a comment
There was a problem hiding this comment.
It seems that everything is okay
Maybe a squashed commit is relevant since 23 commits have been made
maximelefrancois86
left a comment
maximelefrancois86
left a comment
There was a problem hiding this comment.
Looks good, with the minor edits you just did during the heartbeat meeting
andreiciortea
left a comment
andreiciortea
left a comment
There was a problem hiding this comment.
Thanks @danaivach!
|
@NicoRobertIn how do you suggest resolving the conflicts? |
|
The conflict is just on the test reports, which is not that concerning The report should regenerate itself as soon as the test action triggers on main Just make sure that the squash merge does not contains [skip actions] in the commit message so that it triggers If you want a choice just give priority to the report version that is the most recent (the test date should appear in the reports) |
4 participants
This manufacturing scenario motivates the use of concepts defined by the hMAS ontology for the discovery of behavior specifications for sending messages to agents.
See the scenario folder, and the FIPA ontology for further details.
Closes #227