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

Add rultor for continuous integration and fast release #35

Open
emilianodellacasa opened this issue Apr 4, 2019 · 11 comments
Open

Add rultor for continuous integration and fast release #35

emilianodellacasa opened this issue Apr 4, 2019 · 11 comments

Comments

@emilianodellacasa
Copy link
Owner

emilianodellacasa commented Apr 4, 2019

Let's add rultor for continuous integration and for fast release to rubygems, take inspiration from here

@0crat
Copy link
Collaborator

0crat commented Apr 4, 2019

Job #35 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Apr 4, 2019

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

@0crat
Copy link
Collaborator

0crat commented Apr 4, 2019

@emilianodellacasa/z everybody who has role DEV is banned at #35; 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 Apr 9, 2019

@emilianodellacasa/z everybody who has role DEV is banned at #35; 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 Apr 14, 2019

@emilianodellacasa/z everybody who has role DEV is banned at #35; 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 Apr 24, 2019

@emilianodellacasa/z everybody who has role DEV is banned at #35; 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 Apr 29, 2019

@emilianodellacasa/z everybody who has role DEV is banned at #35; 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 4, 2019

@emilianodellacasa/z everybody who has role DEV is banned at #35; 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 9, 2019

@emilianodellacasa/z everybody who has role DEV is banned at #35; 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 14, 2019

@emilianodellacasa/z everybody who has role DEV is banned at #35; 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 19, 2019

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

No branches or pull requests

2 participants