emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Worg: issue with org-tools page
Date: Mon, 31 Jul 2023 16:41:53 +0000	[thread overview]
Message-ID: <87r0ooghim.fsf@localhost> (raw)
In-Reply-To: <ua8mi2$pqf$1@ciao.gmane.io>

Max Nikulin <manikulin@gmail.com> writes:

> 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.

Fair point.

> 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.

That sounds too complex.
I think we can simply add an extra "check" task to
https://git.sr.ht/~bzg/worg/tree/master/item/.build.yml
It will run after "upload", re-exporting files, but not ignoring errors
this time.
WDYT?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2023-07-31 16:42 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
2023-07-31 16:41                     ` Ihor Radchenko [this message]
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=87r0ooghim.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@gmail.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.
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).