search

SWE574-Fall2023-Group1 / SWE574-Fall2023-G1

Project for SWE 574 - Group 1
MIT License
7 stars 1 forks source link

Determine branch use for trivial changes #59

Closed dbaslan closed 1 year ago

dbaslan commented 1 year ago

Hello @SWE574-Fall2023-Group1/backend , I am creating this issue so we can have a permanent answer for everyone to consult. We discussed this before, but I wanted to clarify. When we make trivial changes to the repo such as uploading a new pdf/png/txt file or editing the readme, should we commit directly to the dev branch, or create a new branch to make a pull request? The second method feels like a waste of time for minor contributions, but I'm not sure if the first method will lead to any problems. Any opinions?

ckertam commented 1 year ago

If there is only new file (That should not change any code part!!) for documentation or other informative things, we can directly put them inside the main branch not dev branch. We do not need pr or other things for doc and info files 🛩️

dbaslan commented 10 months ago

Note for future reference: We decided to upload new files and make minor changes on the reports branch, not main or dev.