Posts with #gitflow

#gitflow

Public posts on X that use #gitflow.

Related hashtags

  1. Matthew Skelton@matthewpskelton
    Folks, spare yourself the pain and avoid #GitFlow like the plague. Github Flow, okay. Better: Trunk-Based Development.
    Jakob Ehn @jakobehn
    60K+ downloads of the GitFlow for Visual Studio 2017 extension! More features are in the works, integration with @AzureDevOps pull requests for example
    102159
  2. Jakob Ehn@jakobehn
    60K+ downloads of the GitFlow for Visual Studio 2017 extension! More features are in the works, integration with @AzureDevOps pull requests for example
    0512
  3. Hiro@hirotk_
    Starting a new AI chat for every Gitflow feature branch is the sweet spot to keep the context from getting too bloated. Letting AI handle commit messages also makes diffs clear and easily searchable later. #Gitflow #Git #GameDev #IndieDev #AI
    10230
  4. @[email protected]@jetsetter
    This is how I felt when I found out gitflow is a "legacy Git workflow" that has "fallen in popularity in favor of trunk-based workflows." Atlassian says their gitflow overview is only up for "historical purposes." Thread. #ripvanwinkle @davefarley77
    Download
    42267
  5. @[email protected]@jetsetter
    @jetsetter
    Looking at twitter, I'm not alone in this awakening. The case against git flow is is being actively discussed. @davefarley77 has a recent video on the matter:
    Dave Farley @davefarley77
    Describing GitFlow, Git feature branch-based GitHubFlow and exploring the reasons why they aren’t compatible with the software engineering practices of Continuous Delivery ❌ Watch the video HERE ➡️
    216
  6. Dave Farley@davefarley77
    Describing GitFlow, Git feature branch-based GitHubFlow and exploring the reasons why they aren’t compatible with the software engineering practices of Continuous Delivery ❌ Watch the video HERE ➡️
    Download
    41128
  7. @[email protected]@jetsetter
    @jetsetter
    Anyhow, I'm converting my CI-covered projects to trunk-based workflows and giving git flow up. /thread #RIP #gitflow
    109
  8. Mischa Hildebrand@DerHildebrand
    What's your preferred #git branching model for iOS or Android dev teams? I always thought of #GitFlow as the golden standard, but Atlassian has labeled it as "outdated" on their website. The question is: What's better? And why?
    113
  9. Steve Smith@SteveSmith_Tech
    @SteveSmith_Tech
    Here's an @InfoQ article I did in 2015, explaining why #GitFlow is incompatible with CI let alone CD
    2628
  10. Steve Smith@SteveSmith_Tech
    @SteveSmith_Tech
    Here's an @InfoQ video of a talk I did in 2015, which includes an explanation of why #GitFlow is incompatible with CI
    2214
  11. Steve Smith@SteveSmith_Tech
    @SteveSmith_Tech
    "Given the well-known branch names - master, develop, feature, etc., which branches do we build, which do we test, which do we deploy snapshots, which deploy releases" Snapshots are incompatible with #ContinuousDelivery. They are not reproducible
    1211
  12. Steve Smith@SteveSmith_Tech
    @SteveSmith_Tech
    "Continuous Integration is... the practice of building and integrating code in an automated fashion, every few hours" Nope. It's where every team member commits to master/mainline at least once every 24 hours. And that's impossible with #GitFlow, even if you automerged Develop
    3213
  13. Show more posts