Ma77Ball opened a new pull request, #5622:
URL: https://github.com/apache/texera/pull/5622
### What changes were proposed in this PR?
- Adds a non-blocking GitHub Actions workflow
(`.github/workflows/template-compliance-warning.yml`) that comments when a PR
or issue is opened/edited without following the template, and deletes the
comment automatically once the description is fixed.
- For PRs it strips the template's `<!-- -->` guidance and flags any
required section that is missing or blank; for issues (GitHub form templates
that already enforce required fields) it only flags a fully blank body.
- Keeps the warning wording in `.github/template-compliance-warning.txt` so
editing the message does not touch workflow logic.
- Kept cheap on CI: a single `github-script` job with no build and only a
sparse-checkout of the message file, triggered on `opened`/`edited` (never
`synchronize`), skipping drafts and bots, and posting one self-resolving sticky
comment instead of duplicates.
### Any related issues, documentation, discussions?
Closes: #5621
### How was this PR tested?
- Validated the workflow YAML parses: `python3 -c "import yaml;
yaml.safe_load(open('.github/workflows/template-compliance-warning.yml'))"`.
- Exercised the detection logic in Node against the real
`.github/PULL_REQUEST_TEMPLATE`: an unfilled template flags all three required
sections empty, a properly filled body returns no problems, an empty body and a
template with headings deleted are both flagged, and an issue with content
passes.
- The workflow itself runs only on real `pull_request_target`/`issues`
events, so end-to-end behavior (comment posted then auto-removed) is verifiable
once merged; it cannot run from the PR branch beforehand.
### Was this PR authored or co-authored using generative AI tooling?
Co-authored with Claude Opus 4.8 in compliance with ASF
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
