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 Sep 13, 2021 by Fabian Nuraddin Alexander Gabel's avatar Fabian Nuraddin Alexander Gabel
Hide whitespace changes
Inline Side-by-side
Showing with 3 additions and 5 deletions
+3 -5
  • Workflow.md Workflow.md +3 -5
  • No files found.
Workflow.md
View page @ 02471498
......@@ -40,7 +40,7 @@ Technicians should subscribe to the following labels:
* `tech-maintenance` (Development and standard tasks in order to assure operability that add nono new functionality)
* `typo` (for marginal changes to existing pages that have already undergone quality assurance)
These labels are then specified to inform technical maintainers that something about the webpage, repo does not work as expected or to classify development projects that do not add new functionality (e.g. [code refactoring](https://en.wikipedia.org/wiki/Code_refactoring)).
These labels are then specified to inform technical maintainers that something about the web page, repo does not work as expected or to classify development projects that do not add new functionality (e.g. [code refactoring](https://en.wikipedia.org/wiki/Code_refactoring)).
### Editorial Labels
......@@ -59,8 +59,6 @@ These labels are then specified by the users who need quality assurance on their
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)
## Handling of Merge Requests
> [name=Fabian] I think that this should entirely go to `Contributing.md`.
Every user needs (technical or redactional) needs to adhere to the Contribution-Guidelines.
\ No newline at end of file
Each issue leads to an associated merge request which inherits the chosen labels. Depending on the nature of the chosen labels, either professors or chief-engineers or technicians are responsible to react to the merge request. Redactional changes or new research topics are usually handled by professors of chief-engineers, while maintenance merge requests are handled by technicians.
\ No newline at end of file
Clone repository
  • Continuous Integration and Continuous Deployment
  • Dependencies
  • Editing Markdown
  • Getting Started
  • Integrations
  • Maintenance
  • Postprocessing
  • Preprocessors
  • Program Flow
  • Repository Structure
  • Styleguide
  • Testing
  • Workflow
  • Home