| ... | @@ -73,7 +73,11 @@ This indicates to the contracted service provider (if relevant), that the concep |
... | @@ -73,7 +73,11 @@ This indicates to the contracted service provider (if relevant), that the concep |
|
|
|
|
|
|
|
## Concept Review
|
|
## Concept Review
|
|
|
|
|
|
|
|
Should the developed concept not be concise
|
|
Should the developed concept not be concise or clear enough for the service provider to implement, the status is changed back to ~Concept and reassigned to the project group responsible for developing it. Ensure that the final commit message (for projects with squash merge commits) of the MR title adhere to the [Commit Guidelines](/docs/git/Commit-Guidelines).
|
|
|
|
|
|
|
|
|
See [Danger Checks](/docs/git/Danger-Commit-Checks) for the automated process of checking commit messages on ASAM repositories. Github is still a WIP.
|
|
|
|
|
|
|
|
# Review and merge |
|
|
|
\ No newline at end of file |
|
# Review and merge
|
|
|
|
|
|
|
|
Once the implemented concept is ready for review, a Merge Request [Pull Request] is opened and assigned to the original responsible for the issue. The assignee shall review the implementation for technical accuracy to ensure nothing is lost in translation. The MR must be approved by this assignee and the WIP status of the MR (if present) removed. The CCB performs a final review of the content and merges the MR. The CCB should check for technical alignment with other activities in and outside of the project as well as clear commit messages that adhere to the [Commit Guidelines](/docs/git/Commit-Guidelines). |
|
|
|
\ No newline at end of file |
