Skip to Content

Changes for page Continuous Integration

Last modified by chrisby on 2024/05/05 17:22
From version 2.8
edited by chrisby
on 2024/05/05 17:14
Change comment: There is no comment for this version
To version 2.1
edited by chrisby
on 2024/03/04 21:48
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -12,11 +12,7 @@
12 12  
13 13  ### Code Reviews
14 14  
15 -Requesting and providing code reviews, as on GitHub or GitLab, is a convenient feature for making code reviews asynchronous and remotely available, but it is not the most time-efficient approach for agile teams that do not need these features. For those teams, it is better to maintain high quality code by following these practices:
15 +Requesting and providing code reviews, as on GitHub or GitLab, is a convenient feature for making code reviews asynchronous and remotely available, but it is not the most time-efficient approach for agile teams that do not need these features. For these teams, it is better to maintain high quality code by following these agile practices:
16 16  
17 17  * Code is properly tested, refactored and simplified.
18 -* Code is implicitly reviewed in real time by [[pairing up|doc:Software Engineering.Agile.Extreme Programming.Pair Programming.WebHome]] with technically experienced team members.
19 -
20 -### Developer Branches
21 -
22 -One possible workflow is to create a new branches from main branch, one for each developer in the team. Therefore they are called developer branches and can be named after the team member they stand for. At the beginning of the day, each developer merges the latest main commits to his personal developer branch.
18 +* Code is implicitly reviewed in real time by pairing it with technically experienced team members.