Matt Butler

293 posts

Matt Butler banner
Matt Butler

Matt Butler

@MattButler138

Product Lead for Issues & Projects @GitHub previously 🚢 GitHub Projects, co-founder @zenhubHQ

New Forest, UK 参加日 Nisan 2012
374 フォロー中348 フォロワー
Matt Butler
Matt Butler@MattButler138·
Two highly requested updates today to improve the maintainer experience on GitHub Issues - pinned comments and a new nudge to reduce '+1' comments 🎉
Matt Butler tweet media
English
2
0
3
70
Vladimir Nicolici
Vladimir Nicolici@vnicolici·
@RhysSullivan Yeah, but now many elements no longer automatically update. I have to manually refresh the pages to see updated pull request and action progress, for example.
English
1
0
1
468
Max Kotliar
Max Kotliar@maksim_ka2·
@matthewisabel Opposite experience here: Issues/PRs tabs became a nightmare. The list loads, then reloads a split second later. Any filter changes during that window are lost. I’ve literally trained myself to freeze for a second every time I open it. Started around ~3–6 months ago.
English
2
0
5
917
Matthew Isabel
Matthew Isabel@matthewisabel·
GitHub issues is now much faster. A lot of perf improvements in the queue.
English
75
58
1.1K
519.6K
Matt Butler
Matt Butler@MattButler138·
We just shipped some huge performance improvements when navigating issues from a repo/issues dashboard/projects 🚀🚀🚀 github.blog/changelog/2026…
English
1
10
28
18.3K
Matt Butler
Matt Butler@MattButler138·
@ocornut @github I appreciate that, and we are working hard to fix these things as we find them - so thanks for sharing it. It is now fixed! 🎉 Next up - a whole bunch of performance improvements coming your way 😀
Matt Butler tweet media
English
3
0
39
5.7K
Omar 🍋
Omar 🍋@ocornut·
@MattButler138 @github It’s unfortunately easy to spiral into a circle of snarky complains and being hopeless when the streak of being ignored is not being broken by an enabled and proactive voice. 🙏
English
1
1
34
5.5K
Omar 🍋
Omar 🍋@ocornut·
Was eager to start my week before I realized that @github now refuses to let me see all issues on my own repository??!! It's unacceptable and very stressful. My issues are carefully labelled, but not all interactions are based on label/keyword searches. Let me see my Issues.
Omar 🍋 tweet media
English
20
14
378
39K
Matt Butler
Matt Butler@MattButler138·
@ocornut @github This actually looks like more a recent regression, we did have this limit in place for a while but were able to remove it. We are figuring out why it is back...
English
2
0
6
782
Omar 🍋
Omar 🍋@ocornut·
@MattButler138 @github Thank you Matt for reaching out. I regularly review my issues linearly and it is nice to have the option. If this is some kind of throttling may I suggest it isn’t activated for project maintainers.
English
1
0
3
823
Jared Palmer
Jared Palmer@jaredpalmer·
How can we make @GitHub Issues better for both maintainers and contributors?
English
133
12
335
66.4K
Pablodecortes
Pablodecortes@pablodecortes·
I just tried linking two issues from different repositories, but it doesn’t work — it always adds one as a sub-issue, even when I select “Add existing issue” instead of “Create sub-issue.” I’d like to be able to create issues/tasks/whatever (tied or not tied to a specific repository) and define relationships between them — for example, “this task depends on that one” or “this task is blocked by that task,” etc.
English
1
0
0
27
Matt Butler
Matt Butler@MattButler138·
@awesomekling @jaredpalmer @github Would something like this concept help - where you can create saved/shared views. As an example, a view might filter for label=JS engine or CSS layout. Giving you a quick way to jump between those categories?
Matt Butler tweet media
English
1
0
1
75
Andreas Kling
Andreas Kling@awesomekling·
Not exactly. We're building a web browser at github.com/LadybirdBrowse… and it's composed of many smaller components, but it's all in one big monorepo. It would be super useful for us if we could create issue categories for subcomponents within the monorepo, and browse those independently. Some example categories we might use: "JS engine", "CSS layout", "HTML parser", "Network stack", etc.
English
2
0
2
205
Andreas Kling
Andreas Kling@awesomekling·
@jaredpalmer @github User-defined categories! A single top-level category works fine for the typical small GitHub project, but for bigger projects, being able to create issue categories would be immensely valuable. (Even better if categories can be nested!)
English
1
0
21
1.5K
Matt Butler
Matt Butler@MattButler138·
@pablodecortes @jaredpalmer @github Can you tell me more about the linking? We have recently added parent/child linking (sub-issues) and dependencies. Are there other relationship types that would help?
English
1
0
0
38
Pablodecortes
Pablodecortes@pablodecortes·
Currently GitHub Projects are tightly coupled to repos and issues. I understand the need but I would really like some lightweight alternative of the Linear to not jump back and forth and GitHub projects could become it. 1. Tasks are tied to specific repo. What if my task assumes work in multiple repo? What if I don't really know what repos will be there and just want to create task for investigate? 2. Tasks cannot be easily linked to each other, sometimes it's a nightmare trying to achieve that. 3. I don't actually know because I didn't use projects enough because of the first 2 reasons mainly but if you are looking for life-quality update for github, a lot of people would love to see this happening github.com/orgs/community…
English
1
0
10
830
Bas
Bas@baswollenberg·
@jaredpalmer @pablodecortes @github gotta wonder why it's still not possible to sort issues by created/updated date in Projects. Seems like an incredibly basic thing to want
English
1
0
0
57
dax
dax@thdxr·
@jaredpalmer @github yeah + sort for examples of how we use it, i have a view in linear for "unassigned issues" that we try to keep clear then i have a personal view of issues assigned to me sorted by last updated so i can catch up on activity from commenters
English
3
0
32
1.8K