-
Notifications
You must be signed in to change notification settings - Fork 156
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
announce releases in Telegram #1265
Comments
Job #1265 is now in scope, role is |
@filfreire/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please. |
The user @filfreire/z resigned from #1265, please stop working. Reason for job resignation: It is older than 10 days, see §8 |
Resigned on delay, see §8: -30 point(s) just awarded to @filfreire/z |
@yegor256 Behavior is broken on twitter, should I continue with telegram implementation? |
@paulodamaso/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please. |
@0crat refuse |
@paulodamaso The user @paulodamaso/z resigned from #1265, please stop working. Reason for job resignation: Order was cancelled |
Tasks refusal is discouraged, see §6: -15 point(s) just awarded to @paulodamaso/z |
Just like we do it on Twitter, let's announce them in Telegram chats/groups. Repo owner should be able to configure the name of the group in
.rultor.yml
.The text was updated successfully, but these errors were encountered: