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

Don't overwrite updates made on staging #2

Merged
merged 2 commits into from
Jun 25, 2024
Merged

Conversation

andriokha
Copy link
Member

Scenario

  • Version 1 is deployed to Prod.
  • Version 2 is merged to staging but not yet deployed to Prod. It includes config updates.
  • An admin updates the Drupal site triggering a config export.

Expected result

The config's exported and doesn't clobber version 2's config updates.

Actual result

It will overwrite any changes.

@andriokha andriokha force-pushed the fix-updated-on-main branch 10 times, most recently from abb3e48 to 7586b74 Compare June 25, 2024 09:57
@andriokha andriokha merged commit 7b600db into develop Jun 25, 2024
4 checks passed
@andriokha andriokha deleted the fix-updated-on-main branch June 25, 2024 10:00
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