// use a variable starting with `BUILD_MODULE_` to enable your module
// use a variable starting with `BUILD_MODULE_` to enable your module
// the build variable has to be enabled in the `build.properties.d/` directory.
// the build variable has to be enabled in the `build.properties.d/` directory.
// Otherwise the module will not be activated.
// Otherwise the module will not be activated.
if ("${BUILD_MODULE_EXT_BOTTOM_LINE}"==="ENABLED"){
if ("${BUILD_MODULE_EXT_FLIGHT_PREVIEW}"==="ENABLED"){
caosdb_modules.register(ext_flight_preview);
caosdb_modules.register(ext_flight_preview);
}
}
});
});
...
@@ -69,4 +69,15 @@ If you have unittests (and you should), you need to add a line in :
...
@@ -69,4 +69,15 @@ If you have unittests (and you should), you need to add a line in :
## Update the changelog
## Update the changelog
## Create a merge request
Briefly describe the changes you made to the whole repository in the file called `CHANGELOD.md` in caosdb-webui.
\ No newline at end of file
## Create a merge request
Commit your changes to the repository to a new branch called `f-<custom name>`. `f-` is the shorthand for feature-branch and your custom name should be short, but descriptive, e.g. `f-flight-preview` in this case.
Push your branch upstream using e.g.:
`git push --set-upstream origin f-flight-preview`
Login to gitlab and navigate to the project caosdb-webui.
There should be a button titled `Create Merge Request`.