Skip to content
Snippets Groups Projects
Commit fb6a969a authored by Noah Löwer's avatar Noah Löwer Committed by Martin Schroschk
Browse files

Apply 1 suggestion(s) to 1 file(s)

parent 1b8f34a4
No related branches found
No related tags found
2 merge requests!820Automated merge from preview to main,!818Rm gitlab.yaml file; Add docu on git workflow and ci pipeline
...@@ -42,7 +42,8 @@ pipeline consisting of several checks to ensure compliance with the content rule ...@@ -42,7 +42,8 @@ pipeline consisting of several checks to ensure compliance with the content rule
worry too much about the checks. ZIH staff will help you with that. You will find more information worry too much about the checks. ZIH staff will help you with that. You will find more information
on the [CI/CD pipeline](cicd-pipeline) in the eponymous subsection. on the [CI/CD pipeline](cicd-pipeline) in the eponymous subsection.
The changes on `preview` branch are either automatically merged into the `main` branch on every In order to publish the updates and make them visible in the compendium,
the changes on `preview` branch are either automatically merged into the `main` branch on every
Monday via a pipeline schedule, or manually by admin staff. Moreover, the `main` branch is deployed Monday via a pipeline schedule, or manually by admin staff. Moreover, the `main` branch is deployed
to [https://compendium.hpc.tu-dresden.de](https://compendium.hpc.tu-dresden.de) and always reflects to [https://compendium.hpc.tu-dresden.de](https://compendium.hpc.tu-dresden.de) and always reflects
a production-ready state. Manual interventions are only necessary in case of merge conflicts. The a production-ready state. Manual interventions are only necessary in case of merge conflicts. The
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment