Skip to content

Conversation

@landsman
Copy link
Member

🎈 Describe your changes

Explain briefly your changes, please make sure its explains exactly what you are doing.

📎 Checklist

Please check if the PR fulfills these requirements

  • Mark request as ready for review or draft based on status
  • Fill pull request labels (feature, bugfix, docs etc)
  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation or company wiki
  • I have shared preview link in #dev or #payment-product-team channel and wait for feedback
  • Pull request should be small as possible (much faster code reviews)

@landsman landsman force-pushed the update-cz branch 2 times, most recently from 6d13c13 to b154183 Compare November 22, 2022 10:11
@landsman
Copy link
Member Author

@BubbleB7 FYI: I've split your changes from this pull request: #20 into multiple pull requests.

This will then make the overall change history of our legal documents show the purpose of those changes and where (eu/peru, GDPR / terms) etc at a glance as you can see here.

@landsman landsman mentioned this pull request Nov 22, 2022
@landsman landsman merged commit bd786c8 into master Nov 22, 2022
@landsman landsman deleted the update-cz branch November 22, 2022 11:30
landsman added a commit that referenced this pull request Nov 23, 2022
This was referenced Nov 29, 2022
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.

3 participants