Transprogrammer

823 readers

1 users here now

A space for trans people who code

Matrix Space:

#transprog:socki.moe

Rules:

Don't be a meanie
- no *ism
- consider the feelings of somebody who might read what you say
Don't shitpost
Keep it wholesome
Must be trans / programming related

founded 1 year ago

MODERATORS

[email protected]

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] 4 points 1 year ago

I feel like this is very subjective, but I usually commit whenever a) I have to edit only one thing in a certain file. If I am reasonably sure that I'll only change this one thing in a file, I'll commit b) I feel like what I have just done works, and it is worth writing an explanatory commit comment for: This could be whenever I add or modify a helper function, when I make a new struct, fix a bug, refactor something, etc. c) I am done with it entirely :3

I hope this helps at least a little!