Workflow to do a complete validation of documentation changes against the Camel website
- Dominant language
- Java
- Stars
- 302
- Forks
- 232
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 114
Description
### Description
This is a follow up from https://github.com/apache/camel-quarkus/issues/6041.
While the current workflow is doing the basic format validation it could be nice to if all the checks could run.
There are some limitations on this full check (see https://github.com/apache/camel-quarkus/pull/7891#issuecomment-3443593279).
It might be worth a POC with some added changes in camel-website build commands.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing follow-up issue #6041 and the limitations noted in PR #7891's comment, then inspect the current documentation-validation workflow and the camel-website build commands. Done means a proof of concept that runs the complete applicable checks, with the known limitations documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100