Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • backend backend
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 47
    • Issues 47
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CP - Planta
  • backendbackend
  • Merge requests
  • !16

Merged
Created Oct 19, 2024 by André Sacilotto Santos@andre.santosOwner

Merge Develop into Master considering already tested and displayed out features at sprint 2 presentation's features

  • Overview 0
  • Commits 36
  • Pipelines 2
  • Changes 12

The develop version was uploaded and testes during sprint 2 end's presentation and product delivery. This way, the best practice considering the situation is to merge develop into master(production), even though it's already running on our infrastructure through manual building and deploy.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: develop