Skip to content

fix(ci): enable issue fork jobs on PRs and push to main#130

Merged
rfay merged 2 commits intomainfrom
20260507_less_test_skip
May 7, 2026
Merged

fix(ci): enable issue fork jobs on PRs and push to main#130
rfay merged 2 commits intomainfrom
20260507_less_test_skip

Conversation

@rfay
Copy link
Copy Markdown
Member

@rfay rfay commented May 7, 2026

Summary

  • Both drupal-issue-fork and contrib-issue-fork jobs had github.event_name != 'push' in their if: conditions, silently skipping them on every merge to main
  • They already ran on PRs from the repo owner, making the push exclusion inconsistent with no clear rationale

Test plan

  • Verify Drupal issue fork and Contrib ... issue fork jobs appear and run (not skipped) in CI on this PR

🤖 Generated with Claude Code

rfay and others added 2 commits May 7, 2026 11:50
Both drupal-issue-fork and contrib-issue-fork had github.event_name != 'push'
in their if: conditions, so they were skipped on every merge to main. They
already ran on PRs from the repo owner, so the push exclusion was inconsistent.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
ddev restart after ddev poser was silently swallowed (|| true), so if
restart failed the symlink-project hook never ran, drush en could not
discover the module, and the workspace appeared healthy despite the
module not being enabled.

- ddev restart now retries via stop+start on failure; either path
  triggers symlink-project
- module-not-enabled after drush en now sets SETUP_FAILED=true instead
  of just logging a warning, so SETUP_STATUS.txt reflects the real state

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@rfay rfay merged commit cab430a into main May 7, 2026
16 checks passed
@rfay rfay deleted the 20260507_less_test_skip branch May 7, 2026 18:32
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.

1 participant