Suggested update to git workflow#120
Merged
Merged
Conversation
As a final step when finishing a pull request, the feature/bugfix/enhancement should be added to the release draft document. Look at the drafts "Trigger and action" or the draft for more info.
LukasWikander
approved these changes
Oct 8, 2019
LukasWikander
left a comment
Collaborator
There was a problem hiding this comment.
Perfect! Might be a good idea to let everyone review this though.
Collaborator
|
Also, I know @viktorjo is looking at collecting all our repos in some sort of "project", so it might be nice to have this workflow document there instead. |
Member
Author
|
@viktorjo Have you checked this? Did it work to organise everything into a "project" here on github? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As a final step when finishing a pull request, the feature/bugfix/enhancement should be added to the release draft document. Look at the drafts "Trigger and action" or the draft for more info.
For example, a trigger and action release had we followed this might have looked like this:
TRIGGER AND ACTION RELEASE
Maestro is now able to send basic trigger and action messages enabling a test object to execute predefined actions when specific conditions have been met.
This release is compatible with Maestro Tools x.x.x and Util x.x.x
New Features 🚀
Trigger and Action
#111 Trigger and action file parser. ScenarioControl module can read a trigger and action config file.
#109 Break detection algorithm. ScenarioControl can detect if a test object is braking based on MONR.
#101 C-ITS reads EXAC and ACCM. C-ITS control can now read two trigger and action messages from the message queue.
#90 Trigger Class. A trigger class containing all functionality expected from a trigger.
RVSS and Data Dictionary
Bug Fixes 🐛
Improvements 👍
Other Changes
Issues 💥