presentations/workshop-drupal-automated-testing/drupalcamp-london-2020/code
2025-10-02 23:52:04 +01:00
..
.ddev Move all files to workshop-drupal-automated-testing/drupalcamp-london-2020/ 2025-10-02 23:52:04 +01:00
.github/workflows Move all files to workshop-drupal-automated-testing/drupalcamp-london-2020/ 2025-10-02 23:52:04 +01:00
.idea Move all files to workshop-drupal-automated-testing/drupalcamp-london-2020/ 2025-10-02 23:52:04 +01:00
config Move all files to workshop-drupal-automated-testing/drupalcamp-london-2020/ 2025-10-02 23:52:04 +01:00
web Move all files to workshop-drupal-automated-testing/drupalcamp-london-2020/ 2025-10-02 23:52:04 +01:00
.gitignore Move all files to workshop-drupal-automated-testing/drupalcamp-london-2020/ 2025-10-02 23:52:04 +01:00
composer.json Move all files to workshop-drupal-automated-testing/drupalcamp-london-2020/ 2025-10-02 23:52:04 +01:00
composer.lock Move all files to workshop-drupal-automated-testing/drupalcamp-london-2020/ 2025-10-02 23:52:04 +01:00
phpunit.xml.dist Move all files to workshop-drupal-automated-testing/drupalcamp-london-2020/ 2025-10-02 23:52:04 +01:00
README.md Move all files to workshop-drupal-automated-testing/drupalcamp-london-2020/ 2025-10-02 23:52:04 +01:00
workspace.yml Move all files to workshop-drupal-automated-testing/drupalcamp-london-2020/ 2025-10-02 23:52:04 +01:00

Drupal Automated Testing Workshop: Example Code

Updates

If we need to update any of the commits, the changes should be rebased into the existing commits so that they continue to be in a linear order as per the workshop document.

As we want GitHub Actions to run for each commit, we cant just push the latest commit as that would only trigger a build on the final commit. To do this, we can loop over each of the commit SHAs and push each one separately:

for sha1 in $(git rev-list HEAD --reverse); do
  git push origin $sha1:main --force
done