Skip to content
This repository has been archived by the owner on Feb 23, 2020. It is now read-only.

.drone.yml:61-63: Explore why drone lint and... #208

Closed
0pdd opened this issue Jun 15, 2018 · 2 comments
Closed

.drone.yml:61-63: Explore why drone lint and... #208

0pdd opened this issue Jun 15, 2018 · 2 comments
Assignees
Labels
1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i 1 burning issue bug report Put it to completed tasks temporary list for business

Comments

@0pdd
Copy link
Collaborator

0pdd commented Jun 15, 2018

The puzzle 142-2b52b0ff from #142 has to be resolved:

# @todo #142:60m Explore why drone `lint` and `docker-build` use .env
# Both of them should not as it seems. Write doc why or rm them.
# in case if "Push Hooks" is enabled in Drone settings GUI

The puzzle was created by Artemiy on 15-Jun-18.

Estimate: 60 minutes,

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.

@0pdd
Copy link
Collaborator Author

0pdd commented Jun 15, 2018

@artemiyds2 @duker33 please pay attention to this new issue.

@ArtemijRodionov ArtemijRodionov self-assigned this Jun 15, 2018
@ArtemijRodionov ArtemijRodionov added bug 1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i 1 burning issue labels Jun 15, 2018
ArtemijRodionov added a commit that referenced this issue Jun 16, 2018
* Fix lint pipe

Review fixes

* Apply coala rules

* Add todo for test
@0pdd
Copy link
Collaborator Author

0pdd commented Jun 16, 2018

The puzzle 142-2b52b0ff has disappeared from the source code, that's why I closed this issue. //cc @artemiyds2 @duker33

@0pdd 0pdd closed this as completed Jun 16, 2018
@ArtemijRodionov ArtemijRodionov added the report Put it to completed tasks temporary list for business label Jun 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for this i 1 burning issue bug report Put it to completed tasks temporary list for business
Projects
None yet
Development

No branches or pull requests

2 participants