We originally started setting fetch.prune because it would cause the git module to fail if there were refs locally that were not on the remote (because they got deleted). Based on the Ansible devs' response on https://github.com/ansible/ansible-modules-core/issues/637, we can safely replace this task with setting the "force: true" flag wherever we use the git module.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
callback_plugins | Loading commit data... | |
continuous_delivery | Loading commit data... | |
edx-east | Loading commit data... | |
group_vars | Loading commit data... | |
library | Loading commit data... | |
roles | Loading commit data... | |
sample_vars | Loading commit data... | |
vagrant | Loading commit data... | |
analytics-jenkins.yml | Loading commit data... | |
ansible.cfg | Loading commit data... | |
check_package_upgrades.yml | Loading commit data... | |
create_django_ida.yml | Loading commit data... | |
create_role.yml | Loading commit data... | |
ec2.ini | Loading commit data... | |
ec2.py | Loading commit data... | |
edx_sandbox.yml | Loading commit data... | |
go-agent-docker.yml | Loading commit data... | |
go-agent.yml | Loading commit data... | |
go-server.yml | Loading commit data... | |
inventory.ini | Loading commit data... | |
log_server.yml | Loading commit data... | |
run_role.yml | Loading commit data... | |
security.sh | Loading commit data... | |
security.yml | Loading commit data... | |
vagrant-analytics.yml | Loading commit data... | |
vagrant-cluster.yml | Loading commit data... | |
vagrant-devstack.yml | Loading commit data... | |
vagrant-fullstack.yml | Loading commit data... |