Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for RT #226

Closed
AlexDaniel opened this issue Sep 3, 2017 · 5 comments
Closed

Add support for RT #226

AlexDaniel opened this issue Sep 3, 2017 · 5 comments
Labels
squashable Issues related to Squashable bot

Comments

@AlexDaniel
Copy link
Member

Upcoming SQUASHathon will be about rakudo. Rakudo project does not use github issues, so stock squashable is not going to work (not in a useful way at least). Find a way to add support for http://rt.perl.org/.

@AlexDaniel AlexDaniel added the squashable Issues related to Squashable bot label Sep 3, 2017
@AlexDaniel
Copy link
Member Author

It feels like this should be rejected. There's no proper way to get it working, and (hopefully) we are slowly starting to realize that RT should be abandoned altogether. The stats for the upcoming squashathon will be generated by diffing the state of RT queue before and after the squashathon (so no cool notifications on the channel, sorry but that's life).

@Skarsnik
Copy link
Contributor

Skarsnik commented Oct 1, 2017 via email

@AlexDaniel
Copy link
Member Author

Even if it had some API, https://fail.rakudo.party/ is still as limited. I want a webhook for comments and ticket status changes and I don't think that's going to happen.

I can of course process email notifications from RT. This could work, but I've noticed that these are delayed as well (maybe it's good enough though?).

@AlexDaniel
Copy link
Member Author

I'm inclined to reject this given that we're slowly migrating to github.

@AlexDaniel
Copy link
Member Author

I'm inclined to reject this given that we're slowly migrating to github.

Even more so today! It is possible that we will have RT-focused squashathons in the future, but it's too unlikely that this will be implemented in Squashable just for that one squashathon. Please feel free to work on it, I'll accept a PR, but I don't see this issue moving anywhere in the upcoming years… Rejecting :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
squashable Issues related to Squashable bot
Projects
None yet
Development

No branches or pull requests

2 participants