License requirements for this repo should be documented. Usually done by including a LICENSE plaintext file at top level of repository.
Others can then see what is expected of them if they use or contribute to the repository.
Possible suggestion based on pre-existing uses: MIT license?
https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project
If you’re starting from a blank slate, it’s hard to go wrong with the MIT License. It’s short, very easy to understand, and allows anyone to do anything so long as they keep a copy of the license, including your copyright notice. You’ll be able to release the project under a different license if you ever need to.
License requirements for this repo should be documented. Usually done by including a LICENSE plaintext file at top level of repository.
Others can then see what is expected of them if they use or contribute to the repository.
Possible suggestion based on pre-existing uses: MIT license?
https://opensource.guide/legal/#which-open-source-license-is-appropriate-for-my-project