Re: [PATCH 1/2] ci(check-whitespace): stop requiring a read/write token

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 1/2] ci(check-whitespace): stop requiring a read/write token
From: Junio C Hamano <gitster@xxxxxxxxx>
Date: Wed, 14 Jul 2021 15:20:43 -0700
Cc: git@xxxxxxxxxxxxxxx, "Chris. Webster" <chris@xxxxxxxxxxxx>, Johannes Schindelin <johannes.schindelin@xxxxxx>
In-reply-to: <b54c137cb14527c14bd7c990f9cf32dca50ba5dc.1626300577.git.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Wed, 14 Jul 2021 22:09:36 +0000")
References: <pull.995.git.1626300577.gitgitgadget@gmail.com> <b54c137cb14527c14bd7c990f9cf32dca50ba5dc.1626300577.git.gitgitgadget@gmail.com>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)

"Johannes Schindelin via GitGitGadget" <gitgitgadget@xxxxxxxxx>
writes:

> However, the `check-whitespace` workflow threw a wrench into this plan:
> it _requires_ write access (because it wants to add a PR comment in case
> of a whitespace issue).

OK.

References:
- [PATCH 0/2] check-whitespace: two fixes
  - From: Johannes Schindelin via GitGitGadget
- [PATCH 1/2] ci(check-whitespace): stop requiring a read/write token
  - From: Johannes Schindelin via GitGitGadget

Prev by Date: Re: [PATCH 1/3] doc/git-config: explain --file instead of referring to GIT_CONFIG
Next by Date: Re: Bug report: GIT_CONFIG and user.email/name
Previous by thread: [PATCH 1/2] ci(check-whitespace): stop requiring a read/write token
Next by thread: [PATCH 2/2] ci(check-whitespace): restrict to the intended commits
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux