### Summary The toolbar area with "Files", "Commits", etc. for [my project](https://gitlab.com/maetshju/PraatDocExtractor) is displaying the wrong license, which seems to be a product of the license detection algorithm. It has picked up on the GPLv2 license I have in the COPYING file, when it should have picked up on the COPYING.LESSER file in the repository instead. Having both of these license files in the repository along and named like this is what GNU strongly recommends for using this license on [their website](https://www.gnu.org/licenses/gpl-howto.en.html). I've looked and can't see a way to set the license myself in the project settings, but maybe I'm just overlooking it. Is there a way I can fix this myself? ### Steps to Reproduce * Create a new Project * Add a GPLv2 LICENSE to COPYING * Add a LGPL LICENSE to COPYING.LESSER * Go to Project Overview ### Expected Results * Project license is deemed LGPL ### Actual Results * Project license is deemed GPL ### Additional Detail > You should also include a copy of the license itself somewhere in the distribution of your program. All programs, whether they are released under the GPL or LGPL, should include the text version of the GPL. In GNU programs the license is usually in a file called COPYING. > If you are releasing your program under the LGPL, you should also include the text version of the LGPL, usually in a file called COPYING.LESSER. Please note that, since the LGPL is a set of additional permissions on top of the GPL, it's important to include both licenses so users have all the materials they need to understand their rights. Source: https://www.gnu.org/licenses/gpl-howto.en.html