feat(decision): include study of member - #175
Merged
Merged
Conversation
Study never needed in GEWISWEB, so it was not included in ReportDB at the time. The board would like to have this information available, and to allow this to potentially become part of GEWISGH-146, I have now added the propagation logic. Existing rows are set to Unknown by the migration. They will be updated when the records are regenerated.
tomudding
marked this pull request as ready for review
September 4, 2026 08:20
Member
Author
|
I really hate that it defaults to 'draft' when you use it once. |
This file contains hidden or 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
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
Study never needed in GEWISWEB, so it was not included in ReportDB at the time. The board would like to have this information available, and to allow this to potentially become part of GH-146, I have now added the propagation logic.
Existing rows are set to
Unknownby the migration. They will be updated when the records are regenerated.Related issues/external references
Types of changes