# Pre-Bug report question

**URL:** <https://forum.ansible.com/t/pre-bug-report-question/24708>\
**Category:** Ansible Developer\
**Created:** [June 13, 2017, 10:38am UTC](https://forum.ansible.com/t/pre-bug-report-question/24708 "2017-06-13T10:38:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![LeamHall](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leamhall/32/9390_2.png) [@LeamHall](https://forum.ansible.com/u/LeamHall)\
**Post date:** [June 13, 2017, 10:38am UTC](https://forum.ansible.com/t/pre-bug-report-question/24708/1 "2017-06-13T10:38:57Z")

</div>

In running an old playbook there were deprecation warnings about always\_on.

[DEPRECATION WARNING]: always\_run is deprecated. Use check\_mode = no instead…

There are two very small issues with this; the double periods at the end and the phrase "check\_mode = ". For us newbies “check\_mode: no” would be less confusing.

In looking at the potential to contribute, logging a bug is an easy first step. The secondary question is, for a potential new developer, is this something to fix? Or is the “variable = value” thing a cultural standard?

Thanks!

Leam

---

<div class="post-metadata">

**Author:** ![LeamHall](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leamhall/32/9390_2.png) [@LeamHall](https://forum.ansible.com/u/LeamHall)\
**Post date:** [June 13, 2017, 10:58am UTC](https://forum.ansible.com/t/pre-bug-report-question/24708/2 "2017-06-13T10:58:57Z")

</div>

It would be this line:

[https://github.com/ansible/ansible/blob/devel/lib/ansible/playbook/play\_context.py#L460](https://github.com/ansible/ansible/blob/devel/lib/ansible/playbook/play_context.py#L460)