Update Workflow authored by Benjamin ENGEL (ASAM)'s avatar Benjamin ENGEL (ASAM)
...@@ -63,6 +63,7 @@ Some tips: ...@@ -63,6 +63,7 @@ Some tips:
- Commit and push/pull regularly to prevent headaches! - Commit and push/pull regularly to prevent headaches!
- Use clear commit messages to make sure others understand what you have been doing! (see [Commit Guidelines](../git/Commit-Guidelines)) - Use clear commit messages to make sure others understand what you have been doing! (see [Commit Guidelines](../git/Commit-Guidelines))
- See [Resolving Merge Conflicts](../git/Resolving-Merge-Conflicts) for some tips if you have problems with pushing/pulling to a branch - See [Resolving Merge Conflicts](../git/Resolving-Merge-Conflicts) for some tips if you have problems with pushing/pulling to a branch
- **If there are open questions to other groups or project members - open another issue and assign it to the group/participant! Issues can be linked to the original issue via [Related Issues](https://docs.gitlab.com/ee/user/project/issues/related_issues.html) to make it easy to keep track.**
> Project members for ASAM projects are able to branch directly (see [How to create a Branch](./Branching)). Non-project members will need to use the fork & PR process (see [Forking](./Forking)) > Project members for ASAM projects are able to branch directly (see [How to create a Branch](./Branching)). Non-project members will need to use the fork & PR process (see [Forking](./Forking))
# Concept Implementation # Concept Implementation
... ...
......