Changes for page Development in branches
Last modified by Alexander Schulz-Rosengarten on 2023/09/05 10:52
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,0 +1,1 @@ 1 +Using Git - Content
-
... ... @@ -22,7 +22,7 @@ 22 22 So you took heed to the branching guidelines. There is a little more, you do not know yet when your feature is ready to be merged back into the master branch: 23 23 24 24 1. All planned functionality must be implemented and working 25 -1. Push your branch to the mainline so that itbuildson Bamboo25 +1. Push your branch to the mainline so that Bamboo can build it 26 26 1. The code has to be well commented; especially Javadoc comments have to be complete 27 27 1. The code must not contain any warnings, including FindBugs and Checkstyle warnings. If single warnings cannot be avoided, leave a comment in the source 28 28 1. The code should be well covered by unit tests
- branches.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.XWikiGuest - Size
-
... ... @@ -1,0 +1,1 @@ 1 +13.3 KB - Content
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -249046 31 +2490462 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/249046 3/Development in branches1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/2490462/Development in branches