Change license to GNU GPL v3

[BeepBot99]

The Creative Commons license is not meant for code. It is meant for assets, such as images and videos. I strongly suggest the GNU GPL v3 license. However, if you don't like it, please choose one of these licenses.

[Mesure73L]

Please provide a summary of this license.

[BeepBot99]

Sure! The GNU GPL v3 license (General Public License) is a free license. This means that it gives users freedom over what they can do. It allows for these things:

• Commercial Use
• Redistribution
• Modification
• Private use

However, anyone distributing it must follow these conditions:

• Any redistributions and modifications must have the new source code available to the public.
• The same license must be applied.
• All modifications from the original must be stated.
• There must be proper attribution.

[Mesure73L]

That all sounds good except for commercial use.

[BeepBot99]

By commercial use, it means that they can use it in companies that make money. That means like, they could put ads on it to profit from it. It does not mean that they can force you to pay for it, because they must always have the source code available.

[Mesure73L]

By commercial use, it means that they can use it in companies that make money. That means like, they could put ads on it to profit from it. It does not mean that they can force you to pay for it, because they must always have the source code available.

I know what commercial use means. I don't want that allowed.

[Mesure73L]

What does squash and merge mean?

[BeepBot99]

I already told you in Discord. I know you said no duplicates, but you might not be able to see that now, so I will tell you here anyway. I disabled merge commits because they are really hard to undo without conflicts if there were conflicts when merging. There are two other ways to merge: squash or rebase. By default it is squash, but you can click the dropdown arrow next to it if you want to rebase and merge. Here is what they do:

• Squash and merge puts all of the new commits into one big commit. This makes it easy to undo the pull request if you need to and to see the whole pull request as one feature instead of a lot of little commits. All of the little commits stay in the head branch.
• Rebase and merge puts all of the new commits right into the base branch. There is no merge commit, it just moves all of the new commits. This is useful for undoing individual commits later, but not the entire pull request. The commits are not duplicated though. They are moved, or rebased, from the head branch to the base branch. It is as if all the commits were always originally done in the base branch.
• In case you were wondering, I will explain now what a normal merge commit is and why it is so bad. A merge commit makes two commits. First, it does the last commit done in the head branch, but it is really all of the commits, just under that name. Then, it does a merge commit, which doesn't actually change anything, just says that the branch was merged.