Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silverstripe 5 Compatibility #36

Merged
merged 2 commits into from
May 2, 2024

Conversation

aletail
Copy link
Member

@aletail aletail commented Apr 29, 2024

Summary

Silverstripe 5 Compatibility

Testing Steps

  • Test again (optional)
  • Review Release Notes

Git Flow

  • DO NOT delete "release/*" or "hotfix/*" branches after merging a PR. These are used to publish the next release, and they are deleted automatically.
  • "Squash and merge" is good on "feature/*" into "develop"
  • "Create a merge commit" is good on "release/*" or "hotfix/*" into "main"

github-actions bot and others added 2 commits December 21, 2023 21:06
* Updated composer dependencies
* Before adding/updating an index content check
Empty content is checked for before adding/updating an index. If it is empty the index is not added/updated
@aletail aletail merged commit fb57201 into main May 2, 2024
2 of 3 checks passed
@github-actions github-actions bot deleted the release/2.0.0/silverstripe-5-compatibility branch May 2, 2024 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants