From: Johnny Richard <johnny@johnnyrichard.com>
To: Carlos Maniero <carlos@maniero.me>
Cc: ~johnnyrichard/olang-devel@lists.sr.ht
Subject: Re: [Discussion] The current state of our pipeline
Date: Sat, 17 Feb 2024 17:12:25 +0100 [thread overview]
Message-ID: <dnebdr45gbl5szmfxfldg2t3hxrykeq2gxuudmuo7vxklbceyu@ycdxu7cxwn72> (raw)
In-Reply-To: <CZ72RG5HOAN6.3JJKH3CHLQCP7@maniero.me>
On Sat, Feb 17, 2024 at 01:38:24AM -0300, Carlos Maniero wrote:
> We need to figure out how to run the docs step on the pipeline only on
> pushes.
We can use the $BUILD_REASON in our `upload` task to deploy exclusive
for patchset submission.
> It seems it will only pass when johnny@johnnyrichard.com pushes
> to main.
Yeah, I will be the only one with rights of trigger the pipeline
through pushes at this moment.
> Also it would be nice if maintainers could trigger the pipeline on
> pushes, I can change to account to a paid one but I'm not sure if I'll
> be able to execute the docs step once it is linked to Johnny's account.
I think Sourcehut has a permission management and I should be able to
allow other maintainer with paid account of pushing to our repo.
> At this point it seems easier to remove the step and manually deploy the
> docs.
I think so too. Let's save money, if you need access to deploy the site
I can help you on a video conference.
Johnny Richard
prev parent reply other threads:[~2024-02-17 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 4:38 Carlos Maniero
2024-02-17 16:12 ` Johnny Richard [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=dnebdr45gbl5szmfxfldg2t3hxrykeq2gxuudmuo7vxklbceyu@ycdxu7cxwn72 \
--to=johnny@johnnyrichard.com \
--cc=carlos@maniero.me \
--cc=~johnnyrichard/olang-devel@lists.sr.ht \
/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.johnnyrichard.com/olang.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox