Skip to content

Develop - #8

Open
andriokha wants to merge 7 commits into
mainfrom
develop
Open

andriokha wants to merge 7 commits into
mainfrom
develop

Conversation

@andriokha

Copy link
Copy Markdown
Member

andriokha and others added 7 commits September 4, 2026 16:12
For existing checkouts, updating the repo URL didn't take effect.
Drupal writes an .htaccess into the config directory to block web access
to it. Since 5a3e75a the action's wipe-and-copy has been dotfile-aware on
both sides, so a config repo carrying no .htaccess caused the site's to be
deleted: a security regression.

The .htaccess is not config: it belongs to the site repo. An updated one
(eg. from a core update) lands there first, and any copy carried in the
config repo may be stale. So the action now discards whatever the export
brought and restores the site repo's own from the index, skipping any
whose directory the current export no longer produces.

The host script correspondingly keeps .htaccess out of the config repo,
and drops one an earlier run committed.

Test fixtures now carry differing content on each side (stale-htaccess in
the config repo, site-htaccess in the site repo) so a test can't pass just
because both match. test-existing-pr drops the .htaccess files from the
config repo HEAD to cover the exact regression.
A workflow with a schedule trigger is auto-disabled after 60 days of
repository inactivity, and the disable applies to the whole file: the
push and pull_request runs stop silently along with the cron. That had
already happened, so PRs were running only the host-script bats suite.

The monthly run added little over the push/PR runs, and these tests hit
real GitHub repos with real credentials. workflow_dispatch remains for
ad-hoc runs.
fix: don't delete or overwrite .htaccess
ci: drop the schedule trigger from test.yml
To truly run them in parallel I'd need to add the run ID to the test
branch names, which would make clean-up for failed teardowns more
complicated (right now we can just delete everything with a prefix).
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