You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additionally, there is a message about a detached git HEAD before that in red text (if everything would be working, there would only be green text).
This would never be left broken for such a long time if it was being maintained. I suspect that your developers also use some environment to work on Snowplow and that environment is likely being maintained (and apparently that is a different environment than this one). As such, what is still the purpose of this repository?
The text was updated successfully, but these errors were encountered:
alexanderdean
changed the title
snowplow-batch-pipe-line ansible-playbook is broken and out of date
Removed snowplow-batch-pipe-line ansible-playbook is broken and out of date
Jan 16, 2016
alexanderdean
changed the title
Removed snowplow-batch-pipe-line ansible-playbook is broken and out of date
Remove snowplow-batch-pipe-line ansible-playbook
Jan 16, 2016
alexanderdean
changed the title
Remove snowplow-batch-pipe-line ansible-playbook
Remove snowplow-*-pipe-line ansible-playbooks
Jan 16, 2016
alexanderdean
changed the title
Remove snowplow-*-pipe-line ansible-playbooks
Remove snowplow-*-pipeline ansible-playbooks
Jan 16, 2016
I was just wondering whether you have completely abandoned all development on these ansible-playbooks, since
results in
Additionally, there is a message about a detached git HEAD before that in red text (if everything would be working, there would only be green text).
This would never be left broken for such a long time if it was being maintained. I suspect that your developers also use some environment to work on Snowplow and that environment is likely being maintained (and apparently that is a different environment than this one). As such, what is still the purpose of this repository?
The text was updated successfully, but these errors were encountered: