710
Always commit (lemmy.world)
submitted 2 years ago by to c/programmer_humor@programming.dev
30 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 8 points 2 years ago (2 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 5 points 2 years ago* (last edited 2 years 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 2 years 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.

  • permalink
  • fedilink
  • source
  • parent