From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Worg: issue with org-tools page
Date: Mon, 31 Jul 2023 23:12:49 +0700 [thread overview]
Message-ID: <ua8mi2$pqf$1@ciao.gmane.io> (raw)
In-Reply-To: <87mszdiwt4.fsf@localhost>
On 30/07/2023 16:16, Ihor Radchenko wrote:
> The problem with dependencies is only there for local builds and that's
> probably the motivation of the `condition-case' I proposed to change in
> my patch.
Worg is a set of independent documents, so fail on first error in CI is
reasonable mostly only if a commit may be pushed to the main branch when
it can be built cleanly (a kind of pre-commit check). Otherwise a
contributor may have to struggle with a problem introduced by another
person in a completely unrelated file.
I am unsure if another workflow is suitable for Worg and SourceHut:
changes are pushed to branches. A branch can be merged only if it can be
built successfully. With such approach fail of first error may work.
I hope, there is a better way to address the issue with failure
notifications.
> Without my patch, missing dependencies will simply fail to
> export some .org sources - nothing to worry about unless the file being
> edited is the one that requires missing dependency.
I would set a limit of about a dozen of failures till build process is
not aborted.
next prev parent reply other threads:[~2023-07-31 16:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-09 15:37 Worg: issue with org-tools page Karl Voit
2023-04-09 16:53 ` Ihor Radchenko
2023-04-09 21:51 ` Karl Voit
2023-04-18 12:29 ` Ihor Radchenko
2023-04-18 13:48 ` Karl Voit
2023-07-29 12:14 ` Ihor Radchenko
2023-07-30 2:57 ` Max Nikulin
2023-07-30 6:40 ` Ihor Radchenko
2023-07-30 7:38 ` Max Nikulin
2023-07-30 9:16 ` Ihor Radchenko
2023-07-31 16:12 ` Max Nikulin [this message]
2023-07-31 16:41 ` Ihor Radchenko
2023-08-05 12:14 ` Max Nikulin
2023-08-05 12:23 ` Ihor Radchenko
2023-08-06 11:31 ` Max Nikulin
2023-08-06 15:08 ` Ihor Radchenko
2023-08-09 7:44 ` Ihor Radchenko
2023-08-09 10:35 ` Max Nikulin
2023-08-04 10:21 ` Bastien Guerry
2023-08-05 7:12 ` Ihor Radchenko
2023-08-05 8:50 ` Bastien Guerry
2023-08-05 11:06 ` Ihor Radchenko
2023-08-05 18:07 ` Bastien Guerry
2023-08-06 6:34 ` Ihor Radchenko
2023-08-06 15:17 ` Bastien Guerry
2023-08-07 13:46 ` Ihor Radchenko
2023-08-07 14:26 ` Bastien Guerry
2023-08-10 8:45 ` Ihor Radchenko
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ua8mi2$pqf$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).