How Fleet uses GitHub
Blog post from Fleet
Fleet uses GitHub issues, labels, project boards, and milestones to communicate ownership, priority, status, and proposed release timing, with issue sidebars providing the main at-a-glance reference. Customer feature requests enter a drafting and triage process, may be researched and clarified through “Unpacking the why,” and are prioritized roughly every three weeks during Feature fest before design stories, wireframes, engineering implementation, code review, and QA verification. Larger requests can contain multiple sub-issues with separate milestones, while “quick wins” follow a shorter process. Bug reports follow a more direct workflow of standup triage, prioritization, reproduction when needed, engineering resolution through pull requests, and QA verification. Milestones indicate tentative release versions and dates rather than guarantees, GitHub comments and project statuses provide public updates, and original issue posts are maintained as living source-of-truth documents throughout development.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.