Coverage remained the same when pulling 367e42f7b4a112aa6c4372cf821f756c96bad641 on feature/bootstrap into 6e7d65a9c49052f2b772bff7bb67c704168dae98 on master.
Coverage remained the same when pulling 367e42f7b4a112aa6c4372cf821f756c96bad641 on feature/bootstrap into 6e7d65a9c49052f2b772bff7bb67c704168dae98 on master.
Coverage remained the same when pulling 20ee435ce55555da75210b19f53bfd009766600b on feature/bootstrap into 6e7d65a9c49052f2b772bff7bb67c704168dae98 on master.
Coverage remained the same when pulling fa70267616c2cfd291e91212b58c2e715ab47f53 on feature/bootstrap into 6e7d65a9c49052f2b772bff7bb67c704168dae98 on master.
Coverage remained the same when pulling 4be4ef943c481f6a0d458e4bafa581ba027c5e17 on feature/bootstrap into 6e7d65a9c49052f2b772bff7bb67c704168dae98 on master.
This pull request fixes the following issues:
You can preview the changes within
http://192.168.2.83:8000/en/applications/blog/
:Additional information: