From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mark Greer <mgreer@animalcreek.com>
Cc: oe-linux-nfc@lists.linux.dev
Subject: linux-nfc new repo for workflows
Date: Wed, 21 Oct 2026 21:54:53 +0200 [thread overview]
Message-ID: <38eb16ab-4715-4f6d-9b4b-1e2cf6cfac33@kernel.org> (raw)
Hey Mark,
I want to move the Github CI workflows from neard main branch to
separate repository, because CI just pollutes git history. neard does
not have much of commits on its own, so more than half of recent changes
are just "ci" updates.
It's also logically to have CI development independent of actual code
releases.
That's why I need new repo in linux-nfc: neard-workflow:
https://github.com/linux-nfc/neard-workflow
I am not an admin of linux-nfc organisation so I cannot create it,
therefore maybe you could create it? Or also make me some semi-admin of
linux-nfc organisation, so I would do it myself.
The new repo would look like:
https://github.com/krzk/neard-workflow/
(I split the history of CI commits)
and it seems this approach works correctly:
https://github.com/krzk/neard/actions/runs/39664604766
Best regards,
Krzysztof
next reply other threads:[~2026-10-21 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 19:54 Krzysztof Kozlowski [this message]
2026-10-22 5:22 ` linux-nfc new repo for workflows Mark Greer
2026-10-22 6:55 ` Krzysztof Kozlowski
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=38eb16ab-4715-4f6d-9b4b-1e2cf6cfac33@kernel.org \
--to=krzk@kernel.org \
--cc=mgreer@animalcreek.com \
--cc=oe-linux-nfc@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox