Skip to content

Conversation

@reakaleek
Copy link
Member

Details

⚠️ This PR was created by an automated tool. Please review the changes carefully. ⚠️

Add a workflow that will comment on PRs with AsciiDoc changes.

Why

During the migration to Elastic Docs v3, the Docs team will focus exclusively on migrating content.
To maintain consistency, prevent conflicts, and ensure a smoother transition we will freeze all AsciiDoc changes.

This means you will get a warning when you create AsciiDoc changes in your PRs.

See elastic/docs-builder#281 for details

If there are any questions, please reach out to the @elastic/docs-engineering

@reakaleek reakaleek self-assigned this Jan 28, 2025
@github-actions
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@pquentin
Copy link
Member

The lint failure is not related, however we would like to merge #2769 before merging this.

@miguelgrinberg miguelgrinberg force-pushed the gh-oblt/add-asciidoc-freeze-warning branch from 888e549 to a5072a1 Compare January 28, 2025 15:41
@miguelgrinberg
Copy link
Contributor

Rebasing to get rid of the linter error.

@pquentin pquentin merged commit 3ee42ad into elastic:main Jan 29, 2025
12 of 13 checks passed
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.

3 participants