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

Directives.set() should accept CharSequence #55

Open
yegor256 opened this issue Mar 24, 2015 · 14 comments
Open

Directives.set() should accept CharSequence #55

yegor256 opened this issue Mar 24, 2015 · 14 comments

Comments

@yegor256
Copy link
Owner

Directives.set() should accept CharSequence

@davvd
Copy link

davvd commented Mar 26, 2015

@yegor256 thanks, I added the "bug" tag

@davvd davvd added the bug label Mar 26, 2015
@davvd
Copy link

davvd commented Mar 26, 2015

@yegor256 thanks for tis bug, I topped your account for 15 mins, transaction 000-941ff8d2

@carlosmiranda
Copy link
Collaborator

@0crat in

@0crat 0crat added the scope label Aug 10, 2018
@0crat
Copy link
Collaborator

0crat commented Aug 10, 2018

@0crat in (here)

@carlosmiranda Job #55 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Aug 10, 2018

Bug was reported, see §29: +15 point(s) just awarded to @yegor256/z

@0crat
Copy link
Collaborator

0crat commented Aug 10, 2018

@carlosmiranda/z everybody who has role DEV is banned at #55; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 15, 2018

@carlosmiranda/z everybody who has role DEV is banned at #55; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 20, 2018

@carlosmiranda/z everybody who has role DEV is banned at #55; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 25, 2018

@carlosmiranda/z everybody who has role DEV is banned at #55; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Aug 30, 2018

@carlosmiranda/z everybody who has role DEV is banned at #55; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Sep 4, 2018

@carlosmiranda/z everybody who has role DEV is banned at #55; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Sep 9, 2018

@carlosmiranda/z everybody who has role DEV is banned at #55; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Sep 14, 2018

@carlosmiranda/z everybody who has role DEV is banned at #55; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@0crat
Copy link
Collaborator

0crat commented Sep 19, 2018

@carlosmiranda/z everybody who has role DEV is banned at #55; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

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

Successfully merging a pull request may close this issue.

4 participants