1
0
forked from docs/doc-exports
Artem Goncharov dfe3039259
switch to git apply of the generated patch (#12)
switch to git apply of the generated patch

In comparison to a regular diff we have binary files already in patch. It is also created with the purpose to be shared (by email). Try applying it instead.

Reviewed-by: OpenTelekomCloud Bot <None>
2022-05-10 11:01:59 +00:00
2022-05-03 05:20:12 +00:00
2022-05-03 05:20:12 +00:00
2022-05-03 05:20:12 +00:00
2022-03-08 10:25:35 +01:00
2022-05-03 05:20:12 +00:00
2022-04-27 16:05:48 +00:00
2022-04-27 16:05:48 +00:00
2022-05-03 05:20:12 +00:00
2022-05-09 09:53:23 +00:00

doc-exports

Repository to track document exports, not for public use

Document sources (in HTML) are placed under docs//

In the there are files docs_.yaml that describe required data for the particular document. For all of the documents configured in those files conversion from HTML to RST will be attempted. In addition to that a patch file (changes in the RST format) will be generated.

Automatic pull request proposal

Change for any of the documents configured in the docs_.yaml would trigger job to propose corresponding changes to the target repository. This is implemented in the following way:

  • HTML content from the pull request will be converted with the latest conversion script (otc_doc_convertor) to RST (new)

  • HTML content for the same document from current main branch with the corresponding version of the conversion script will be converted to RST (base).

  • New state is compared against base and corresponding patch file is generated

  • Resulting patch file is force-applied in the target repository (skipping all conflicts) and PR is created

Description
Open Telekom Cloud Doc Exports
Readme 316 MiB
Languages
Python 86.6%
Jinja 13.4%