this post was submitted on 26 Aug 2023
20 points (100.0% liked)

Transprogrammer

823 readers
1 users here now

A space for trans people who code

Matrix Space:

Rules:

founded 1 year ago
MODERATORS
[email protected]
20
When should I commit on projects? (pricefield.org)
submitted 1 year ago by [email protected] to c/[email protected]
11 comments fedilink hide all child comments
 

I am currently working on a small project, and I am working on getting it functional, but I question when exactly should I make commits. I usually just do it when I am done with working on it, but I know in practical projects often times commits are for one specific thing but given the project does not even work yet what exactly do I do.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 1 year ago (1 children)

For my team, we create branches off of dev to start working on a specific feature. It’s really up to the dev how often they commit to that branch but I recommend often to prevent losing any work. Once the feature is done we merge the branch to dev and roll all of the commits into one so looking at the history on dev, each commit represents 1 feature.

[–] [email protected] 1 points 1 year ago (1 children)

for me at this moment I don't think branches are super relevant to me at the moment since the project does not yet function. I feel like it will function by next commit. also one question I have about dev branches is that how is it that I can compile and use the dev branch on some projects,, like how do they work on code that is not yet functional and would break compiling the software until it is completed.

[–] [email protected] 1 points 1 year ago

Oh yeah so our project is well established so different situation.

The feature branches are small complete pieces and they shouldn’t be breaking dev.

If this is a personal project, just commit whenever you want. At least when you’re finished working so you don’t lose your work.