ppkarwasz opened a new pull request, #4288: URL: https://github.com/apache/logging-log4j2/pull/4288
Same clean-up as #4286, applied to `2.26.x`. GitHub evaluates `schedule`, `issues`, `issue_comment` and `workflow_run` triggers only on the default branch, so these copies were dead code: - `close-stale` (`schedule`) - `labeler` (`issues`, `issue_comment`) - `process-dependabot` (`workflow_run`, the `2.x` copy handles PRs against every branch) `analyze-dependabot` stays, since `pull_request` runs the file from the PR merge commit. `deploy-site` now only stages the website for `release/2.26.*` branches. The staging site for `2.x` and the production site (from `2.x-site-pro`) are deployed by the workflow on `2.x`, so the `2.x`-guarded jobs never ran here. No changelog entry, since this only touches CI configuration. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_014QXFCr2hQv3zoVf7wo5Lab -- 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]
