Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
research-topics-mat-tuhh research-topics-mat-tuhh
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Fabian Nuraddin Alexander Gabel
  • research-topics-mat-tuhhresearch-topics-mat-tuhh
  • Wiki
  • Workflow

Workflow · Changes

Page history
Update Workflow authored May 11, 2021 by Fabian Nuraddin Alexander Gabel's avatar Fabian Nuraddin Alexander Gabel
Hide whitespace changes
Inline Side-by-side
Showing with 5 additions and 1 deletion
+5 -1
  • Workflow.md Workflow.md +5 -1
  • No files found.
Workflow.md
View page @ 4463e0af
......@@ -14,7 +14,7 @@ This does not mean to only change a file, but to have one dedicated issue/merge-
## Localized Notification and (Quality) Assurance
By the use of [labels](https://collaborating.tuhh.de/cfg0846/research-topics-mat-tuhh/-/labels), the classification of issues allows to only notify the ones that are needed during the handling of the follow-up merge-request:
The use of [labels](https://collaborating.tuhh.de/cfg0846/research-topics-mat-tuhh/-/labels) during issue creation allows to only notify the ones that are needed during the handling of the follow-up merge-request. There are different types of labels available
### General Labels
......@@ -46,6 +46,10 @@ Professors, Chief-Engineers and other people responsible for editorial quality a
These labels are then specified by the users who need quality assurance on their research topic by their supervisor.
### Other Labels
New labels can be added by everyone but the subscription needs to be carried out individually. Therefore it is better to reuse existing labels.
# DRAFT: Implementation (open for discussion)
> [name=Fabian] I think that this should entirely go to `Contributing.md`.
......
Clone repository
  • Continuous Integration and Continuous Deployment
  • Dependencies
  • Editing Markdown
  • Getting Started
  • Integrations
  • Maintenance
  • Postprocessing
  • Preprocessors
  • Program Flow
  • Repository Structure
  • Styleguide
  • Testing
  • Workflow
  • Home