Request a Demo
Home   >   mailing lists

Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs - Mailing list pgsql-hackers

From Nazir Bilal Yavuz
Subject Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs
Date
Msg-id CAN55FZ3Z2hVcZA+VRp-VzAYKAD-i+WYzSrqjgyYmRL3rMmT7sA@mail.gmail.com
Whole thread Raw
In response to Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs
Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs
List pgsql-hackers
Tree view 
Hi,

Sorry for the late reply.

On Fri, 6 Oct 2023 at 17:07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> As a quick cross-check, I searched our commit log to see how many
> README-only commits there were so far this year.  I found 11 since
> January.  (Several were triggered by the latest round of pgindent
> code and process changes, so maybe this is more than typical.)
>
> Not sure what that tells us about the value of changing the CI
> logic, but it does seem like it could be worth the one-liner
> change needed to teach buildfarm animals to ignore READMEs.

I agree that it could be worth implementing this logic on buildfarm animals.

In case we want to implement the same logic on the CI, I added a new
version of the patch; it skips CI completely if the changes are only
in the README files.

-- 
Regards,
Nazir Bilal Yavuz
Microsoft
Attachment

pgsql-hackers by date:

Previous
From: Federico
Date:
Subject: Re: Improve upcasting for INT range and multi range types
Next
From: Heikki Linnakangas
Date:
Subject: Re: Simplify newNode()