Fixed permission handling for member data #256 #258
edraft
commented 2023-03-24 14:23:39 +01:00
Owner
No description provided.
edraft
added 1 commit 2023-03-24 14:23:39 +01:00
Fixed permission handling for member data #256
87b277515c
edraft
requested review from Ebola-Chan 2023-03-24 14:23:42 +01:00
edraft
self-assigned this 2023-03-24 14:23:44 +01:00
edraft
added this to the Sprint 1.0.0 project 2023-03-24 14:23:46 +01:00
edraft-dev
removed review request for Ebola-Chan 2023-03-25 18:01:17 +01:00
edraft-dev
requested review from edraft-dev 2023-03-25 18:01:17 +01:00
edraft-dev
approved these changes 2023-03-25 18:01:25 +01:00
edraft
merged commit f56dbf8e2a into 1.0.0 2023-03-25 18:01:58 +01:00
edraft
deleted branch #256 2023-03-25 18:01:58 +01:00
edraft
referenced this issue from a commit 2023-03-25 18:01:58 +01:00
Merge pull request 'Fixed permission handling for member data #256' (#258) from #256 into 1.0.0
Ebola-Chan
approved these changes 2023-03-25 23:00:10 +01:00
No reviewers
Labels
No Label
MVP
web-interface
bug
bugfix
cli
discussion
documentation
duplicate
expense
high
expense
low
expense
medium
expense
very-high
help wanted
improvement
invalid
priority
blocker
priority
high
priority
low
priority
medium
question
refactoring
release
story
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sh-edraft.de/sh_discord_bot#258
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "#256"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?