这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@inetol
Copy link
Member

@inetol inetol commented May 8, 2025

This PR is part of #4707

@return42
Copy link
Member

return42 commented May 8, 2025

As far as I can tell, the PR looks good to me ... shall we switch from DRAFT to "Ready For Review”?

@inetol inetol marked this pull request as ready for review May 8, 2025 14:22
…n.yml

documentation.yml will run after integration.yml COMPLETES successfully (will
defer anything depending on integration.yml until heavy loads like container
building are moved to separate workflows) and in master branch.

Style changes, cleanup and improved integration with CI by leveraging the use of
shared cache between all workflows (not functional until all workflows have been
refactored).
@return42 return42 force-pushed the rework-documentation branch from 896bf31 to f559bdb Compare May 8, 2025 15:39
@return42 return42 merged commit 48801db into searxng:master May 8, 2025
6 checks passed
@inetol inetol deleted the rework-documentation branch May 8, 2025 21:01
@return42
Copy link
Member

return42 commented May 9, 2025

documentation.yml will run after integration.yml COMPLETES successfully

just verified .. and it works :-)

https://github.com/searxng/searxng/commits/gh-pages/

.. time to say one more: thanks a lot for all your work!

@dalf dalf mentioned this pull request May 9, 2025
@dalf
Copy link
Contributor

dalf commented May 9, 2025

I ask here and then open an issue if this is confirm:

@inetol, is it intended? I see these points as an issue.


This comment applied to #4734 too.

@unixfox
Copy link
Contributor

unixfox commented May 9, 2025

Additional context : The workflow does not run in PR anymore. So it's not testing the code of a PR that change something related to the documentation.

Bnyro pushed a commit to Bnyro/searxng that referenced this pull request Jun 25, 2025
…n.yml (searxng#4733)

documentation.yml will run after integration.yml COMPLETES successfully (will
defer anything depending on integration.yml until heavy loads like container
building are moved to separate workflows) and in master branch.

Style changes, cleanup and improved integration with CI by leveraging the use of
shared cache between all workflows (not functional until all workflows have been
refactored).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants