this post was submitted on 27 Nov 2023
294 points (94.8% liked)

Programming

17503 readers
8 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
 

Edit:

Since theres been some confusion with dates

In 2016 github made site side searching login only and hid the search bar if you werent logged in. This didnt include searching within a repository so that could still be done, just not all repositories

This year was the change being referred to in this link which made repository level searching require logging in

Blog post: https://github.blog/changelog/2023-06-07-code-search-now-requires-login/

you are viewing a single comment's thread
view the rest of the comments
[–] Kuinox@lemmy.world 4 points 1 year ago* (last edited 1 year ago) (2 children)

You used the wrong search bar, you just used the one for the file list.
There is a search icon on the top right.

[–] lysdexic@programming.dev 2 points 1 year ago (1 children)

You used the wrong search bar, you just used the one for the file list.

The fact that one of the excuses for GitHub search results being subpar is that there is a right and a wrong search bar is already telling.

[–] Kuinox@lemmy.world 0 points 1 year ago

The fact you call it "search results being subpar" tell me you never used the big top search bar labeled "Type / to search".
You can't make an interface that everyone will understand, there will always be a percentage of user who will be lost.