All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: linux-wpan@vger.kernel.org
Cc: alex.aring@gmail.com, miquel.raynal@bootlin.com,
	david.girault@qorvo.com,
	Stefan Schmidt <stefan@datenfreihafen.org>
Subject: [PATCH 9/9] workflow: add reuse job to check for REUSE compliance
Date: Sun, 24 Sep 2023 14:22:31 +0200	[thread overview]
Message-ID: <20230924122231.716878-10-stefan@datenfreihafen.org> (raw)
In-Reply-To: <20230924122231.716878-1-stefan@datenfreihafen.org>

The linter ensures we can catch problems early on and keeps the codebase
reuse compliant. A big step for ard for all downstream users who care
about license compliance and SBOM generation.

As extra step we generate a SBOM file as artifact.

Signed-off-by: Stefan Schmidt <stefan@datenfreihafen.org>
---
 .github/workflows/reuse.yml | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 .github/workflows/reuse.yml

diff --git a/.github/workflows/reuse.yml b/.github/workflows/reuse.yml
new file mode 100644
index 0000000..194a7d7
--- /dev/null
+++ b/.github/workflows/reuse.yml
@@ -0,0 +1,19 @@
+# SPDX-FileCopyrightText: 2023 Stefan Schmidt <stefan@datenfreihafen.org>
+#
+# SPDX-License-Identifier: ISC
+
+name: Check for REUSE compliance of wpan-tools
+on: push
+
+jobs:
+  reuse:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Check out repository
+      uses: actions/checkout@v4
+    - name: Install reuse tool
+      run: pip3 install reuse
+    - name: Run reuse lint
+      run: reuse lint
+    - name: Create SBOM
+      run: reuse spdx > sbom.txt
-- 
2.41.0


  parent reply	other threads:[~2023-09-24 12:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24 12:22 [PATCH 0/9] wpan-tools: switch to SPDX header for license and copyright Stefan Schmidt
2023-09-24 12:22 ` [PATCH 1/9] m4: remove empty folder which only holds a .gitignore file Stefan Schmidt
2023-09-24 12:22 ` [PATCH 2/9] license: clearly indicate license in file name and use new LICENSES folder Stefan Schmidt
2023-09-24 12:22 ` [PATCH 3/9] wpan-ping: switch files to SPDX header for license and copyright Stefan Schmidt
2023-09-24 12:22 ` [PATCH 4/9] wpan-hwsim: " Stefan Schmidt
2023-09-24 12:22 ` [PATCH 5/9] src/nl802154.h: switch file " Stefan Schmidt
2023-10-01 23:33   ` Alexander Aring
2023-10-02 13:29     ` Stefan Schmidt
2023-09-24 12:22 ` [PATCH 6/9] examples: switch files " Stefan Schmidt
2023-09-24 12:22 ` [PATCH 7/9] src: " Stefan Schmidt
2023-09-24 12:22 ` [PATCH 8/9] misc: switch remaining " Stefan Schmidt
2023-09-24 12:22 ` Stefan Schmidt [this message]
2023-09-25  7:22 ` [PATCH 0/9] wpan-tools: switch " Miquel Raynal
2023-09-26  7:58   ` Stefan Schmidt
2023-10-01 23:37     ` Alexander Aring
2023-10-02 13:29       ` Stefan Schmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230924122231.716878-10-stefan@datenfreihafen.org \
    --to=stefan@datenfreihafen.org \
    --cc=alex.aring@gmail.com \
    --cc=david.girault@qorvo.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.