You are viewing a single thread.
View all comments
36 points

Is this post about Github seemingly detecting an incorrect licence? The project was relicenced in a later commit, so I dont think this behavior is entirely wrong.

permalink
report
reply
7 points

that’s why it’s wrong

permalink
report
parent
reply
9 points

What should it do instead? I think the only reasonable action would be not showing it if the licence file was changed.

permalink
report
parent
reply
9 points

IMO it should be re-recognizing it every time the license file is changed, but only showing a “click here to learn more about different licenses” would also be much better

permalink
report
parent
reply
22 points

Plus, the license was only changed on a secondary branch. The default branch still has the MIT license. The text at the top isn’t “this is the license file you have open” it’s “the repo is licensed under this” so it’s correct behavior but bad UX. It would be most user-friendly to show repo license and then also say “this branch has an invalid license, beware shenanigans”

permalink
report
parent
reply
5 points

I didn’t even realize that! Their official distribution page links to the “secondary branch”, which is actually an outdated tag branch. The license was changed a month ago.

permalink
report
parent
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

  • Keep content in english
  • No advertisements
  • Posts must be related to programming or programmer topics

Community stats

  • 3.3K

    Monthly active users

  • 806

    Posts

  • 12K

    Comments