From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: common/travis/xlint: make xlint only fatal for new templates
Date: Sun, 22 Oct 2023 03:46:24 +0200 [thread overview]
Message-ID: <20231022014624._dmI7WH5z4hkp_rdDHiHxSLwYps-dGhcIcMExNDITiU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44930@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
There's a closed pull request on the void-packages repository
common/travis/xlint: make xlint only fatal for new templates
https://github.com/void-linux/void-packages/pull/44930
Description:
per discussion on irc, to help updates and other changes go more smoothly, xlint should only cause a CI failure if the linted template is new.
examples:
- succeeds because only a changed template errors: https://github.com/void-linux/void-packages/actions/runs/5496798220/jobs/10017025380
- fails because of a new package with errors: https://github.com/void-linux/void-packages/actions/runs/5496783595/jobs/10017001341
this does not affect the *reporting* of lint issues, those are still produced as annotations on the 'files changed' tab.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
prev parent reply other threads:[~2023-10-22 1:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 22:28 [PR PATCH] " classabbyamp
2023-07-08 22:29 ` [PR PATCH] [Updated] " classabbyamp
2023-07-08 22:41 ` classabbyamp
2023-07-08 22:42 ` classabbyamp
2023-07-08 22:44 ` classabbyamp
2023-07-08 22:51 ` classabbyamp
2023-07-08 22:53 ` classabbyamp
2023-07-08 22:55 ` classabbyamp
2023-07-08 22:58 ` classabbyamp
2023-07-08 23:00 ` classabbyamp
2023-07-08 23:02 ` classabbyamp
2023-10-07 1:45 ` github-actions
2023-10-22 1:46 ` github-actions [this message]
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=20231022014624._dmI7WH5z4hkp_rdDHiHxSLwYps-dGhcIcMExNDITiU@z \
--to=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).