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

gitstrap.go:272-273: Extract name resolution logic and... #25

Closed
0pdd opened this issue Jul 7, 2019 · 19 comments
Closed

gitstrap.go:272-273: Extract name resolution logic and... #25

0pdd opened this issue Jul 7, 2019 · 19 comments

Comments

@0pdd
Copy link

0pdd commented Jul 7, 2019

The puzzle 9-5fb1349f from #9 has to be resolved:

gitstrap/gitstrap.go

Lines 272 to 273 in 575aff7

// @todo #9:30m/DEV Extract name resolution logic
// and repo lookup logic below into separate functions.

The puzzle was created by @vassilevsky on 24-Jun-19.

Estimate: 30 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0crat
Copy link

0crat commented Jul 7, 2019

@g4s8/z please, pay attention to this issue

@0crat 0crat removed their assignment Jul 7, 2019
@0crat 0crat added the scope label Jul 7, 2019
@0crat
Copy link

0crat commented Jul 7, 2019

Job #25 is now in scope, role is DEV

@0crat
Copy link

0crat commented Jul 7, 2019

The job #25 assigned to @vassilevsky/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; there will be a monetary reward for this job

@0crat
Copy link

0crat commented Jul 12, 2019

@vassilevsky/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.

@vassilevsky
Copy link
Contributor

@0crat wait for my availability

@0crat 0crat added the waiting label Jul 15, 2019
@0crat
Copy link

0crat commented Jul 15, 2019

@0crat wait for my availability (here)

@vassilevsky The impediment for #25 was registered successfully by @vassilevsky/z

@github-actions
Copy link

@g4s8 ping (issue is stale)

@github-actions github-actions bot added the stale label Sep 10, 2019
@g4s8
Copy link
Owner

g4s8 commented Sep 10, 2019

@0crat continue

@0crat 0crat removed the waiting label Sep 10, 2019
@0crat
Copy link

0crat commented Sep 10, 2019

@0crat continue (here)

@g4s8 @g4s8/z continued working on job #25

@0crat
Copy link

0crat commented Sep 10, 2019

The user @vassilevsky/z resigned from #25, please stop working. Reason for job resignation: It is older than 10 days, see §8

@0crat
Copy link

0crat commented Sep 10, 2019

Resigned on delay, see §8: -30 point(s) just awarded to @vassilevsky/z

@0crat
Copy link

0crat commented Sep 10, 2019

@g4s8/z everybody who has role DEV is banned at #25; 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

0crat commented Sep 15, 2019

@g4s8/z everybody who has role DEV is banned at #25; 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

0crat commented Sep 20, 2019

@g4s8/z everybody who has role DEV is banned at #25; 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

0crat commented Sep 25, 2019

@g4s8/z everybody who has role DEV is banned at #25; 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

0crat commented Sep 30, 2019

@g4s8/z everybody who has role DEV is banned at #25; 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)

@0pdd
Copy link
Author

0pdd commented Sep 30, 2019

The puzzle 9-5fb1349f has disappeared from the source code, that's why I closed this issue.

@0pdd 0pdd closed this as completed Sep 30, 2019
0pdd referenced this issue Sep 30, 2019
Fixed repo create bug
@0crat 0crat removed the scope label Sep 30, 2019
@0crat
Copy link

0crat commented Sep 30, 2019

Job gh:g4s8/gitstrap#25 is not assigned, can't get performer

@0crat
Copy link

0crat commented Sep 30, 2019

The job #25 is now out of scope

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