Suche Ergebnisse

54 Lesezeichen - Sortieren nach: Datum ↓ / Titel / Stimmen /

  1. I remember reading the original GitFlow article back when it first came out. I was deeply unimpressed - I thought it was a weird, over-engineered solution to a non-existent problem. I couldn't see a single benefit of using such a heavy approach. I quickly dismissed the article and continued to use Git the way I always did (I'll describe that way later in the article). Now, after having some hands-on experience with GitFlow, and based on my observations of others using (or, should I say more precisely, trying to use) it, that initial, intuitive dislike has grown into a well-founded, experienced distaste. In this article I want to explain precisely the reasons for that distaste, and present an alternative way of branching which is superior, at least in my opinion, to GitFlow in every way.
    http://www.endoflineblog.com/gitflow-considered-harmful
    Schlagwörter: , , , , von Stefan Macke (2016-01-30)
    Stimmen: 0
  2. A taxonomy of version control strategies for and against Continuous Integration
    This series of articles describes a taxonomy for different types of Feature Branching – developers working on branches in isolation from trunk – and how Continuous Integration is impacted by Feature Branching variants.
    http://www.alwaysagileconsulting.com/articles/version-control-strategies
    Schlagwörter: , , , , von Stefan Macke (2016-01-30)
    Stimmen: 0
  3. -
    https://github.com/ValveSoftware/steam-for-linux/issues/3671
    Stimmen: 0
  4. Der Gitflow Workflow definiert ein striktes Branching-Modell, das rund um das Projekt-Release gestaltet wurde. Es ist ein wenig komplizierter als der Feature Branch Workflow, stellt aber einen stabilen Systemrahmen für den Umgang mit größeren Projekten bereit.
    https://www.atlassian.com/de/git/workflows#!workflow-gitflow
    Schlagwörter: , , , , , , von Stefan Macke (2014-10-27)
    Stimmen: 0
  5. As someone who’s always felt fairly comfortable in Git, I thought sharing some of the nuggets I learnt with the community might help someone to find an answer without needing to do lots of research.
    http://www.andyjeffries.co.uk/25-tips-for-intermediate-git-users
    Schlagwörter: , , , , von Stefan Macke (2014-10-11)
    Stimmen: 0
  6. Code reviews are a great way to improve code quality, catch bugs, and keep your whole team in sync with the latest changes. My favorite tool for doing a code review is still Github’s Pull Request feature, because of the easily-accessible diffs, inline comments, and commit-level and PR-level views of the file changes.
    http://blog.originate.com/blog/2014/09/29/effective-code-reviews
    Stimmen: 0
  7. -
    http://git-scm.com/book/ch8-2.html
    Schlagwörter: , , , von Stefan Macke (2014-10-03)
    Stimmen: 0
  8. -
    http://alistapart.com/article/git-the-safety-net-for-your-projects
    Schlagwörter: , , , , , von Stefan Macke (2014-09-09)
    Stimmen: 0
  9. Liste kostenloser Programmierbücher
    https://github.com/vhf/free-programming-books
    Stimmen: 0
  10. Type commands. See their effect in real time. Perfect rendering for presentations.
    https://github.com/Readify/GitViz
    Schlagwörter: , , , , von Stefan Macke (2014-09-07)
    Stimmen: 0

Seitenanfang

neueste Lesezeichen / vorherige / weitere / älteste Lesezeichen / Seite 1 von 6

Impressum - Angetrieben von SemanticScuttle