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.

Sign up for GitHub

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

Jump to bottom

Add CI #1

Open
duker33 opened this issue Jan 30, 2018 · 0 comments
Open

Add CI #1

duker33 opened this issue Jan 30, 2018 · 0 comments
Labels
1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for it 3 we can defer this issue. But it'll good to implement it dev task about development. Some markup or code take it any teammate can take this issue and start working with it

Comments

@duker33
Copy link
Contributor

duker33 commented Jan 30, 2018 •
edited
Loading

Continuous integration

Check for success app building.

Example here:
https://github.com/fidals/shopelectro
@duker33 duker33 added 1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for it 2 hours some big and monolith issues. For example with hard decisions or discussions take it any teammate can take this issue and start working with it dev task about development. Some markup or code 3 we can defer this issue. But it'll good to implement it and removed 2 hours some big and monolith issues. For example with hard decisions or discussions labels Mar 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1 hour typical issue size. It's one pdd hour. Performer should spend about one astronomical hour for it 3 we can defer this issue. But it'll good to implement it dev task about development. Some markup or code take it any teammate can take this issue and start working with it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@duker33