Bring back sorting code search results by date!
GitHub introduces sub-issues, issue types and advanced search
51–60 of 213 posts
Re: GitHub introduces sub-issues, issue types and advanced search
#52Re: GitHub introduces sub-issues, issue types and advanced search
#53this happens after I've moved everything to height. downside is it was a lot of work. upside is height is amazing and I'm pleased with the choice. anyone else using it?
what is height?
Re: GitHub introduces sub-issues, issue types and advanced search
#54Great, a few more decades and it might become a usable bugtracker. What's next on the list? Maybe priority/severity or status/resolution? I helped on a quite large open source project for some time and loved working with Bugzilla. The announced switch to Github for that project was one reason I lost interest. I even prefer to work with a well administrated(!) Jira over Github issues.
> well administrated Jira Based on my experience that doesn't exist. Hell even if it did, Jira is sooooo unbelievably slow I would still take literally anything else. Maybe even Savannah. A colleague joked that we need a "waiting for Jira" Jira task.
[dead]
Re: GitHub introduces sub-issues, issue types and advanced search
#55Instead of these features I want them to stop spam issues on my repos. All the issues I've gotten in the last year on my project are completely nonsensical. It's not even spam it's just like random URLs or complete nonsense from freshly created accounts that aren't trying to sell anything or just the issue template. And every time it costs me 2 clicks to click on "report" then I have to type "spam", click the spam category, then I have to type "it's spammmmmmmmmmmmmmmmmmmmmm" to hit the 15 character report description requirement, then I have to solve a captcha. All this despite the fact that I've had a GitHub account for like a decade and I've filed like 30+ spam reports, none of which were frivolous.
I opened GitHub after typing this comment and there it was, a notification from an obvious bot account opening an issues that's just 5 meaningless Korean letters with no description.
Re: GitHub introduces sub-issues, issue types and advanced search
#56Earlier quoted context omitted.
What doesn't work?
If you search code for a string you know is there it is completely git or miss if it is found. Always has been like that. Also see https://news.ycombinator.com/item?id=35144250
I assumed you were talking about issue search, since that's what the thread is about.
Re: GitHub introduces sub-issues, issue types and advanced search
#57Earlier quoted context omitted.
What doesn't work?
If you search code for a string you know is there it is completely git or miss if it is found. Always has been like that. Also see https://news.ycombinator.com/item?id=35144250
Oh yeah, where on the Internet does this work reliably?please don’t say gitlab
Re: GitHub introduces sub-issues, issue types and advanced search
#58I would like it if Github could fix all the bugs with back button (broken browser history) first
Re: GitHub introduces sub-issues, issue types and advanced search
#59> This means there are no new UI patterns to slow you down, Sure there are, it's a common UI design mistake - you can't do advanced without breaking the basics: previously you could filter your issues with a drop-down filter in 2 clicks. The PR tab still has this (inconsistency) while the new issue requires a worse and longer path that uses a typed field, bringing up you phone keyboard as a downside
Longer paths, especially ones like these that require keyboard input, are especially painful from an accessibility perspective, where for most cases such typed fields make things take exponentially longer than if it can be achieved by just clicks/tabs/arrows.
Re: GitHub introduces sub-issues, issue types and advanced search
#60Earlier quoted context omitted.
If you search code for a string you know is there it is completely git or miss if it is found. Always has been like that. Also see https://news.ycombinator.com/item?id=35144250
Oh yeah, where on the Internet does this work reliably?please don’t say gitlab
Sourcegraph.