• Anticorp
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year 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
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      1 year 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
      link
      fedilink
      arrow-up
      2
      ·
      1 year 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.