drift@pvv email -> gitea issue automation #157
Labels
No Label
dns
exploration
gitea
new stuff
services
software
art
backup
big
blocked
bug
crash report
disputed
documentation
duplicate
enhancement
good first issue
logging
nixos
question
salt
security
servers n' hardware
wontfix
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Drift/issues#157
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Is it too much spam, or is this a good idea? Perhaps a human-in-the-loop system where we approve which emails to turn into issues
As a user seeking support from drift, I would not appreciate if my ticket was made public to everyone on the internet, so it would at least have to be a separate and private board, not this one. Also, there are other, good, ticketing systems to manage user support. I tried running all the drift-emails into osTicket a year or two ago, and wasn't really happy with it. However,
rt
seems good, maybe we could try that?anything that supports us coordinating and tracking the response would be nice. Too often do we fail to reply-all when responding to emails. I was imagining using the "incoming email" feature in gitea to basically turn the resulting issue into an email thread.
We have talked about doing it in matrix before (lol)
Maybe this is duplicate-ish of #97?