You are correct you can remove the file and then check your community profile, and you’ll see the option to add a license once again.

As far as the branches, we only look at the license on the default branch, and apply that to the whole repository.

Awesome, that’s all great to know. Thank you so much for your quick and concise reply! 😄

If you want to change the license of an existing GitHub repository, you can follow these steps:

1. Remove the Existing License:

   • Delete the existing LICENSE file in your repository. This file usually contains the text of the license and may be named differently depending on the license type.

2. Update SPDX Identifiers:

   • Go through the source code and documentation in your repository and update any references to the old license's SPDX identifier.

3. Commit Changes:

   • Commit your changes to the repository.

4. Add New License:

   • GitHub should automatically detect the absence of a license file and provide an option to add a new license.
   • Navigate to your repository on GitHub.
   • Click on "Add file" and then choose "Create new file."
   • Name the file LICENSE and select the license template you want to use.
   • Commit the new LICENSE file.

5. Propagation to Other Branches:

   • If you have multiple branches, the license change should be applied automatically when you merge or rebase branches. However, you can ensure consistency by following these steps:
     • If you are working with branches, make the license change in one branch, then merge or rebase other branches onto the branch with the license change.
     • If you are working with forks, make the change in the upstream repository, and contributors can update their forks accordingly.

Remember to communicate the license change to contributors and users of your repository. Changing a license is a significant action, and it's essential to ensure that everyone is aware of and agrees with the change.

Profile

AKASHDIP MAHAPATRA
"everything is physics bro"
E=mc²

thanks 4 the article

Hey!
to add a license to an existing project, you can go to "insights" near "settings", and select "Community Standards", there your project is compared to an recommended community standard; Naturally a standard project has a license. If Your own doesn't have it, choose "Add a license", choose a license and commit changes.

For sure, the previous answers are also a way to got it!