Ticket 446: Add subject to ticket thread in Discord #6
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
added 7 commits
February 10, 2024 12:34
…amps. test cases pass
…s only touched when changed (not every sync)
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.
When netbot creates a thread to sync with a ticket, using the
/thread xyzslash command, netbot will add the ticket subject to the thread name.This PR adds pylint as a standard build tool, and a lot of related code clean up.
This PR adds an abstraction to assure python datetime is used consistently (which was a big problem).
This PR adds a per-ticket lock during synchronization, so concurrent attempts to sync the same ticket will fail gracefully.