• Marc EdwardsMarc Edwards, over 4 years ago

    I am absolutely loving this combination:

    • GitHub Issues for actionable items and single tasks.
    • GitHub projects boards and GitHub milestones for big picture targets.
    • Twist threads for discussion, usually prior to opening GitHub Issues for the tasks.
    9 points
    • Bart Claeys, over 4 years ago

      Exactly how I work!

      1 point
    • Fabian ValkenbergFabian Valkenberg, over 4 years ago

      Interesting choice. Why does work best for you? Never thought of Github as the place for design progress / tasks

      0 points
      • Marc EdwardsMarc Edwards, over 4 years ago

        It’s really important to separate Git (the scary version control used by developers) from GitHub Issues (the awesome and very friendly web based service for discussions around a specific topic).

        You don’t need to use Git to use GitHub Issues or GitHub projects. I’d say GitHub Issues or GitHub projects are as easy to use as any other similar service. They’re incredibly enjoyable to use if you like Markdown, too.

        If you also use Git, the integration is amazing.

        2 points
    • Mike A.Mike A., over 4 years ago

      So you have a separate repo for every project and there are related tasks (issues)? Would love to hear more detail...

      0 points
      • Marc EdwardsMarc Edwards, over 4 years ago

        Yep, that’s pretty much it. One repo per project, and all related actionable items (adding features and fixing bugs) are added to GitHub Issues and assigned to a person. You don’t even need a Git client installed to use GitHub’s website.

        0 points