LF-4240: April 2024 data policy updates (Version 6: May 31, 2024) #3217
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* update ¿Dónde almacenamos sus datos?
kathyavini
reviewed
May 30, 2024
packages/webapp/src/containers/Consent/locales/en/Worker.Consent.md
Outdated
Show resolved
Hide resolved
packages/webapp/src/containers/Consent/locales/en/Worker.Consent.md
Outdated
Show resolved
Hide resolved
packages/webapp/src/containers/Consent/locales/en/Worker.Consent.md
Outdated
Show resolved
Hide resolved
packages/webapp/src/containers/Consent/locales/en/Owner.Consent.md
Outdated
Show resolved
Hide resolved
- add missing space Co-authored-by: Joyce Yuki <[email protected]>
- fix typo Co-authored-by: Joyce Yuki <[email protected]>
* remove unnecessary section
* correct who funds LiteFarm link
* correct who funds LiteFarm link
* correct Información sobre la Administración de la Finca section
* fix ¿Cómo utilizamos los datos? section * add missing part to ¿Dónde almacenamos sus datos?
* fix format in Como usamos os dados?
* add version date
* add version date * fix typo
* add version date
* add version date * fix typo
* add version date * fix typo
* add version date
* add version date
SayakaOno
changed the title
SayakaOno
requested review from
Duncan-Brain and
kathyavini
and removed request for
a team
kathyavini
previously approved these changes
Jun 4, 2024
kathyavini
previously approved these changes
Jun 5, 2024
Duncan-Brain
reviewed
Jun 5, 2024
| * @returns { Promise<void> } | ||
| */ | ||
| export const up = async function (knex) { | ||
| await knex('userFarm').update('has_consent', false); |
There was a problem hiding this comment.
@kathyavini made a good point about migrations files ordering. Just wanted to clarify if the intended order is to merge directly into main, then back into integration afterwards? Or does it matter?
There was a problem hiding this comment.
I don't think the order will make any difference. We will:
- merge this PR to integration
- create a release branch that includes the code changes in this PR + version update and merge into main
- merge main to integration
* fix email etc.
* fix email
* delete 'lote'
kathyavini
approved these changes
Jun 5, 2024
Duncan-Brain
approved these changes
Jun 5, 2024
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jun 5, 2024
…UPDATES Revert "Merge pull request #3217 from LiteFarmOrg/LF-4240/April_2024_data_policy_updates"
16 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Data policy updates (Version 6: May 31, 2024).
Branched out from the main branch.
Jira link: https://lite-farm.atlassian.net/browse/LF-4240