Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs
От | Nazir Bilal Yavuz |
---|---|
Тема | Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs |
Дата | |
Msg-id | CAN55FZ3KJBBonoqe4mrJUSCz0XyoEaLzjDwGLE+j9ihwsBwD0w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs (Daniel Gustafsson <daniel@yesql.se>) |
Ответы |
Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs
|
Список | pgsql-hackers |
Hi, Thanks for the reply! On Fri, 8 Sept 2023 at 11:05, Daniel Gustafsson <daniel@yesql.se> wrote: > > > On 7 Sep 2023, at 18:06, Nazir Bilal Yavuz <byavuz81@gmail.com> wrote: > > > if the changes are only in the docs, don't run > > all tasks except building the docs task; this could help to save more > > CI times. > > A related idea for docs in order to save CI time: if the changes are only in > internal docs, ie README files, then don't run any tasks at all. Looking at > src/backend/parser/README the last two commits only touched that file, and > while such patches might not be all that common, spending precious CI resources > on them seems silly if we can avoid it. > > It doesn't have to be included in this, just wanted to bring it up as it's > related. I liked the idea, I am planning to edit the 0002 patch. CI won't run any tasks if the changes are only in the README files. > Almost, but not entirely. There are a set of scripts which generate content > for the docs based on files in src/, like src/backend/catalog/sql_features.txt > and src/include/parser/kwlist.h. If those source files change, or their > scripts, it would be helpful to build docs. Thanks! Are these the only files that are not in the doc subfolders but effect docs? Regards, Nazir Bilal Yavuz Microsoft
В списке pgsql-hackers по дате отправления: