Closed nazrhyn closed 9 years ago
I got the design for the async project/label fetches implemented for a single project. Need to expand to multiple projects then put it in place for startup. Then on to issue modification handling.
Almost completed this today. Issues are tracked based on per-project "relevant labels" configuration. Here are some examples:
The issue title (as a link) needs to be added to the modified notification; I need to update the CHANGELOG, add some more information to the README and then I'll be pushing these changes. This upcoming push will fix #8 and #9, as well.
What do you think @spodlecki?
+1 Looks great to me, though we don't really use gitlab issue tracking -- we host those through JIRA. We do use the Merge Requests though
Yeah, I admit to having completely ignored that for similar reasons: we don't use the merge requests.
@spodlecki No idea if you still use this, but just did a big rewrite and now support MRs and wiki page events. https://github.com/nazrhyn/gitlab-slack/releases/tag/2.0.0
Add label change tracking by keeping track of existing issue label state and monitoring the issues on update events.