b7f285d733
Provide all licenses used in the project in a LICENSES folder and add SPDX license and copyright information for all files in accordance with the Reuse Software[0] specification. The copyright information is based on the file's git history, using a fairly generous definition of "non-trivial". As of the spec recommendation, the information is generally added as comments in the files themselves, except for - NEWS, README and similar top-level standard files, so that a SPDX code isn't the first thing people encounter - files that don't support comments (json) or where they'd be a bit awkward (.desktop, .service) - anything under po/, to not interfere with translation teams Those are covered by a .reuse/dep5 files, except for image assets, where separate .license files are used (It would be possible to add comments to SVG files, but I don't trust image editors to preserve them). [0] https://reuse.software/ Part-of: <https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/merge_requests/224>
18 lines
740 B
YAML
18 lines
740 B
YAML
# SPDX-FileCopyrightText: 2021 Florian Müllner <fmuellner@gnome.org>
|
|
#
|
|
# SPDX-License-Identifier: GPL-2.0-or-later
|
|
|
|
patterns:
|
|
deny:
|
|
- regex: '^$CI_MERGE_REQUEST_PROJECT_URL/(-/)?merge_requests/$CI_MERGE_REQUEST_IID$'
|
|
message: Commit message must not contain a link to its own merge request
|
|
- regex: '^extensions/'
|
|
message: Commit message subject should not be prefixed with 'extensions/', use the extension name instead
|
|
where: subject
|
|
- regex: '^[^:]+: [a-z]'
|
|
message: "Commit message subject should be properly Capitalized. E.g. 'window: Marginalize extradicity'"
|
|
where: subject
|
|
- regex: '^\S*\.js:'
|
|
message: Commit message subject prefix should not include .js
|
|
where: subject
|