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

File.createTempFile should be forbidden #877

Closed
krzyk opened this issue Apr 26, 2018 · 14 comments
Closed

File.createTempFile should be forbidden #877

krzyk opened this issue Apr 26, 2018 · 14 comments
Assignees

Comments

@krzyk
Copy link
Collaborator

krzyk commented Apr 26, 2018

Create a rule to forbid any usage of File.createTempFile, in error message suggest using Junit @Rule TemporaryFolder.

@krzyk
Copy link
Collaborator Author

krzyk commented Apr 26, 2018

@0crat help

@0crat
Copy link
Collaborator

0crat commented Apr 26, 2018

@0crat help (here)

@krzyk Can't understand "help", try one of these:

  • assign Assign a performer to this issue
  • boost Set a boost for the job
  • hello Just say hello
  • in Register this issue in scope (WBS)
  • out Close the order and remove this job from scope
  • pay Pay a user some extra cash
  • quality Review a task
  • resign Resign from this issue
  • status Check the status of the job
  • version Print current version of the bot
  • wait Register an impediment for a job

@krzyk
Copy link
Collaborator Author

krzyk commented Apr 27, 2018

@0crat in

@0crat 0crat added the scope label Apr 27, 2018
@0crat
Copy link
Collaborator

0crat commented Apr 27, 2018

@0crat in (here)

@krzyk Job #877 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Apr 27, 2018

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

@0crat
Copy link
Collaborator

0crat commented Apr 27, 2018

@krzyk/z everybody who has role DEV are banned at this job; 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 May 2, 2018

@krzyk/z everybody who has role DEV are banned at this job; 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)

@krzyk
Copy link
Collaborator Author

krzyk commented May 7, 2018

@0crat assign me

@0crat
Copy link
Collaborator

0crat commented May 7, 2018

@0crat assign me (here)

@krzyk The job #877 assigned to @krzyk/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this

@0crat
Copy link
Collaborator

0crat commented May 7, 2018

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @krzyk/z

@0crat
Copy link
Collaborator

0crat commented May 7, 2018

It is strongly discouraged to assign jobs to their creators, see §19: -15 point(s) just awarded to @krzyk/z

krzyk added a commit to krzyk/qulice that referenced this issue May 7, 2018
krzyk added a commit to krzyk/qulice that referenced this issue May 7, 2018
krzyk added a commit to krzyk/qulice that referenced this issue May 7, 2018
krzyk added a commit to krzyk/qulice that referenced this issue May 7, 2018
@krzyk
Copy link
Collaborator Author

krzyk commented May 7, 2018

@krzyk done

@krzyk krzyk closed this as completed May 7, 2018
@0crat 0crat removed the scope label May 7, 2018
@0crat
Copy link
Collaborator

0crat commented May 7, 2018

Order was finished: +30 point(s) just awarded to @krzyk/z

@0crat
Copy link
Collaborator

0crat commented May 7, 2018

The job #877 is now out of scope

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

No branches or pull requests

2 participants