Skip to content
This repository has been archived by the owner on Jun 20, 2023. It is now read-only.

Fix: Update German privacy notice (EXPOSUREAPP-2832) #1230

Merged
merged 1 commit into from Sep 25, 2020

Conversation

janetback
Copy link
Contributor

Checklist

  • Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
  • If this PR comes from a fork, please Allow edits from maintainers
  • Set a speaking title. Format: {task_name} (closes #{issue_number}). For example: Use logger (closes # 41)
  • Link your Pull Request to an issue - Pull Requests that are not linked to an issue with you as an assignee will be closed, except for minor fixes for typos or grammar mistakes in documentation or code comments.
  • Create Work In Progress [WIP] pull requests only if you need clarification or an explicit review before you can continue your work item.
  • Make sure that your PR is not introducing unnecessary reformatting (e.g., introduced by on-save hooks in your IDE)
  • Make sure that your PR does not contain changes in text files, therefore the PR must not contain changes in values/strings/* and / or assets/* (see issue [HELP WANTED][README] Text / Translations  #332 for further information)
  • Make sure that your PR does not contain compiled sources (already set by the default .gitignore) and / or binary files

Description

@janetback janetback requested review from ralfgehrer and a team September 25, 2020 03:18
@ralfgehrer ralfgehrer added 1.4.0 and removed 1.4.0 labels Sep 25, 2020
@ralfgehrer ralfgehrer merged commit 9a0a152 into release/1.4.x Sep 25, 2020
@ralfgehrer ralfgehrer deleted the fix/string-typos-privacy branch September 25, 2020 06:55
@ralfgehrer ralfgehrer changed the title Update privacy_de.html (EXPOSUREAPP-2832) Fix: Update German privacy notice (EXPOSUREAPP-2832) Sep 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants