Sina Rohde (0b857114) at 01 Feb 10:27
Insert a meaningful description for this merge request here. What is the
new/changed behavior? Which bug has been fixed? Are there related Issues?
Point the reviewer to the core of the code change. Where should they start
reading? What should they focus on (e.g. security, performance,
maintainability, user-friendliness, compliance with the specs, finding more
corner cases, concrete questions)?
How to set up a test environment for manual testing?
Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines
For further good practices have a look at our review guidelines.
Wieso hier kein Link zu den anderen Projekten?
Hier sollte die Unterstreichung so lang sein wie der Text drüber. Das ist aber nur eine Kleinigkeit.
Insert a meaningful description for this merge request here. What is the
new/changed behavior? Which bug has been fixed? Are there related Issues?
Point the reviewer to the core of the code change. Where should they start
reading? What should they focus on (e.g. security, performance,
maintainability, user-friendliness, compliance with the specs, finding more
corner cases, concrete questions)?
How to set up a test environment for manual testing?
Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines
For further good practices have a look at our review guidelines.
Daniel Hornung (0b857114) at 14 Dec 14:33
FIX: Added section title back.
Insert a meaningful description for this merge request here. What is the
new/changed behavior? Which bug has been fixed? Are there related Issues?
Point the reviewer to the core of the code change. Where should they start
reading? What should they focus on (e.g. security, performance,
maintainability, user-friendliness, compliance with the specs, finding more
corner cases, concrete questions)?
How to set up a test environment for manual testing?
Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines
For further good practices have a look at our review guidelines.
Sina Rohde (0c891af2) at 13 Dec 07:28
Merge remote-tracking branch 'origin/dev' into f-overview
... and 7 more commits
Daniel Hornung (7447acd6) at 10 Nov 10:35
Daniel Hornung (94d85578) at 10 Nov 10:35
FIX: Pipeline and dependencies
Daniel Hornung (7447acd6) at 10 Nov 09:51
WIP: Pipeline and dependencies
Daniel Hornung (b60a8617) at 10 Nov 08:09
WIP: Pipeline and dependencies
Daniel Hornung (1f39dfbe) at 10 Nov 08:08
WIP: Pipeline and dependencies
Sina Rohde (16700af1) at 07 Nov 15:08
back to overview
Sina Rohde (5614f0e1) at 07 Nov 15:07
Henrik tom Wörden (5614f0e1) at 05 Oct 13:31
MAINT: Rename CaosDB to LinkAhead
Daniel Hornung (0dd16d65) at 01 Sep 10:54
DOC: Better documentation hints in MR template.
Daniel Hornung (ddb8bd70) at 24 Feb 11:55
MR template: JSON schema checklist item.