Repository Structure and Branches

DTUComputeCognitiveSystems / deep_detektor

Automated Factual-Claim Detection in Danish Broadcasting

Other

2 stars 0 forks source link

Open sfvnielsen opened 6 years ago

sfvnielsen commented 6 years ago

How should we strucutre the repository and our code to make it easy to use and manage

JesperLH commented 6 years ago

I suggest the following,

We should strive for object oriented code
One "master" branch which is only for working code.
Several feature or development branches (which are added to the "master" branch once they are "production" ready")

philipjhj commented 6 years ago

To build on what Jesper suggested - what about we go all the way and use HubFlow as described here.

NorthGuard commented 6 years ago

I think HubFlow is waaay over the top. I agree with a couple of branches, but classic GitHub should have more than we need.