Add GitPython's Standard License Header Comments to Shell Scripts#1907

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

Byron merged 2 commits intogitpython-developers:mainfromDaveLak:add-license-header-comments-to-shell-scripts

Apr 23, 2024

Merged

Add GitPython's Standard License Header Comments to Shell Scripts#1907

Byron merged 2 commits intogitpython-developers:mainfromDaveLak:add-license-header-comments-to-shell-scripts

Apr 23, 2024

Conversation

Copy link

Contributor

DaveLak commentedApr 22, 2024

This is related to follow-ups for unresolved review comments in#1901. Specifically:#1901 (comment)

See the commit messages for2b0a969 andb021a76 for further details.

CC@EliahKagan for visibility

DaveLak added2 commits

April 22, 2024 16:36

Add GitPython's standard license header comments to oss-fuzz scripts

2b0a969

These files are already BSD-3-Clause even without the headers, butadding these comments and the `LICENSE-BSD` symlink to the root level`LICENSE` file are helpful to reinforce that there are only twoparticular files in the `fuzzing/` that are not under BSD-3-Clause.See:gitpython-developers#1901 (comment)

Add GitPython's standard license header comments to top level scripts

b021a76

While discussing adding similar license comments to the shell scriptsintroduced in PRgitpython-developers#1901, it was noticed that the shell scripts in therepository root directory did not have such comments and suggested thatwe could add them when the scripts in the `fuzzing/` directory wereupdated, so this commit does just that.See:gitpython-developers#1901 (comment)