Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
N
neutrinet_cube_install
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Neutrinet
  • neutrinet_cube_install
  • Issues
  • #11

Closed
Open
Opened Nov 18, 2019 by Ilja@iljaOwner

Add develop branch

We now merge directly into master. Since we want master to be working at all time, this means:

  • Every merge needs to be fully tested
  • big chance of breaking things in master if bugs do slip through the net

Having a develop branch could help here because you can limit testing specific to the feature that's added/bug that's fixed. Every now and then develop can be merged into master after a full run of the script.

This worklow should be added to the README.md

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: Neutrinet/neutrinet_cube_install#11