This allows us to filter our team board to identify when we are planning for things to go out.įor the volunteer work I do I make use of Trello and its GitHub integration. Using Milestones for Release Tracking: we follow a consistent milestone naming convention across repos (the date).We then have our Development Team board which all the developers work from as we track all our work through the development process. These thin project boards are just used to track project completion and where the requirement is driven from. These thin project boards are completely driven by automations so no user interaction required. For our actual "projects" we have going, we have really "thin" project boards. Tagging Issues and PRs across multiple Project Boards: this is an interesting one to explain.Multi Repo Boards at an Organisation Level: you can have multi repo boards if they are part of an organisation (so either paying for the Teams subscription or an Open Source organisation).Project Board Automations: the ability to have issues and pull requests automatically move based on whether it's been closed, reopened or PR changes requested was a huge draw card for our team.Reasons we've dived into GitHub Projects include: Only the developers use this as we have to work with a bunch of different teams using different requirements trackers.
For work we have dived completely into using GitHub Projects.
0 kommentar(er)
