716
Always commit (lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
[-] Anticorp@lemmy.ml 8 points 11 months ago

You should be pushing feature branches as you work on them, so if you have a crash or something, your work isn't lost. Builds should be triggered from pull requests on the main branch, if triggered by anything. You should never push directly to main. At least that's my preference.

[-] Zeth0s@lemmy.world 5 points 11 months ago* (last edited 11 months ago)

Our ci/cd pipelines build also feature branches. I do push often, clean code. I don't push when I am tired enough that I can't trust my judgment that the code I am pushing is over my personal quality threshold. I add meaningful, concise commit messages. These are my rules.

[-] TheManuz@lemmy.world 2 points 11 months ago

I make WIP branches only for that purpose, so I can push half done work and rework it the day after.

This means a lot of history changes, but only in the WIP branch.

When history is clean, I rebase the feature branch.

Is this a good practice? I never found a better way to backup partial code.

this post was submitted on 15 Sep 2023
716 points (97.2% liked)

Programmer Humor

18907 readers
398 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS