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 tags to tweets #561

Closed
yegor256 opened this issue Aug 20, 2014 · 22 comments
Closed

add tags to tweets #561

yegor256 opened this issue Aug 20, 2014 · 22 comments

Comments

@yegor256
Copy link
Owner

Let's add language tags to tweets, getting them from here: https://developer.github.com/v3/repos/#list-languages

@alex-palevsky
Copy link
Contributor

I'll ask someone to take care of this task soon

@alex-palevsky
Copy link
Contributor

thanks for reporting! I topped your account for 15 mins, transaction 000-e970b5bb

@alex-palevsky
Copy link
Contributor

@aistomin it's yours now, please proceed keeping in mind our principles. Feel free to ask any technical questions right here in the ticket

@alex-palevsky
Copy link
Contributor

@aistomin The cost of this task is 30 mins (this is exactly how much will be paid, not less not more), when the task is done

@alex-palevsky
Copy link
Contributor

@aistomin you're working with this ticket for the last 13 days. If it's not closed within the next 16 hours, it will be re-assigned to someone else, see No Obligations principle

@alex-palevsky
Copy link
Contributor

@aistomin the task is overdue, and I have to re-assign it to someone else. Please, stop working with it immediately. In general, we're against overdue tasks, check this page

@alex-palevsky
Copy link
Contributor

@krzyk please proceed, it's yours

@krzyk
Copy link

krzyk commented Oct 18, 2014

@alex-palevsky waiting for jcabi/jcabi-github#923

@yegor256
Copy link
Owner Author

@alex-palevsky looks like we'll need more time here

@alex-palevsky
Copy link
Contributor

@alex-palevsky looks like we'll need more time here

@yegor256 right, take your time and thanks for informing

krzyk pushed a commit to krzyk/rultor that referenced this issue Dec 27, 2014
@alex-palevsky
Copy link
Contributor

the code made here contains a puzzle 561-e08f2fc3, which will be resolved soon

krzyk pushed a commit to krzyk/rultor that referenced this issue Jan 24, 2015
@krzyk
Copy link

krzyk commented Jan 25, 2015

PR #761

krzyk pushed a commit to krzyk/rultor that referenced this issue Jan 28, 2015
@krzyk
Copy link

krzyk commented Jan 28, 2015

@yegor256 change has been merged to master, please close this issue

@yegor256
Copy link
Owner Author

@rultor release, tag is 1.48

@yegor256
Copy link
Owner Author

@krzyk thanks!

@rultor
Copy link
Collaborator

rultor commented Jan 28, 2015

@rultor release, tag is 1.48

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Collaborator

rultor commented Jan 28, 2015

@rultor release, tag is 1.48

@yegor256 Oops, I failed. You can see the full log here (spent 1hr)

@yegor256
Copy link
Owner Author

@rultor release, tag is 1.48

@rultor
Copy link
Collaborator

rultor commented Jan 28, 2015

@rultor release, tag is 1.48

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Collaborator

rultor commented Jan 28, 2015

@rultor release, tag is 1.48

@yegor256 Done! FYI, the full log is here (took me 16min)

@alex-palevsky
Copy link
Contributor

@krzyk 30 mins sent to your balance (ID 50961141), many thanks!; +30 added to your rating, at the moment it is: +3312

@alex-palevsky
Copy link
Contributor

the last puzzle 561-e08f2fc3/#698 originated from here solved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants