lanl / BEE

Other
13 stars 3 forks source link

Update Developer's Guide: Explain our Git Workflow #867

Open pagrubel opened 5 days ago

pagrubel commented 5 days ago

We need to explain our Git workflow: Things like branch names for issues or features: If there is an issue it should be of this format issue#/ e.g. issue857/mpi-integration-test If there isn't an issue consider making one for the fix or feature Lifetime branches develop and main and how we use them should be explained in the developer's manual We make all our PR's on a feature or issue branch that will be merged into develop after test and review We have github IC tests that must pass before merge to develop can take place We also have overnight tests that must pass before anything can go into main Main branch is reserved for releases