Add new field acknowledgement and adjacent visibility fields #11
jrenslin
commented 2022-03-29 16:49:51 +02:00
Owner
No description provided.
jrenslin
added the 2022-03-29 16:49:51 +02:00
kind/feature
label
jrenslin
self-assigned this 2022-03-29 16:49:51 +02:00
jrenslin
added the 2022-03-29 17:25:45 +02:00
status/done
label
jrenslin
referenced this issue from a commit 2022-03-29 17:25:52 +02:00
Add new field acknowledgement and adjacent visibility fields
jrenslin
closed this issue 2022-03-29 17:25:52 +02:00
Labels
No Label
kind/breaking
kind/bug
kind/dependencies
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/done
status/needs-feedback
kind/breaking
kind/bug
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/done
status/needs-feedback
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: museum-digital/csvxml#11
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?