# RunOnChange=True
**URL:** https://forum.liquibase.org/t/runonchange-true/7617
**Category:** General Discussion
**Created:** [December 9, 2022, 1:49am UTC](https://forum.liquibase.org/t/runonchange-true/7617 "2022-12-09T01:49:57Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@SreekanthReddyU](https://forum.liquibase.org/u/SreekanthReddyU)
#### Post date: [December 9, 2022, 1:49am UTC](https://forum.liquibase.org/t/runonchange-true/7617/1 "2022-12-09T01:49:57Z")
Is there is a way we can set RunOnChange=true in master changelog file ? rather rhan adding it to each individual change set.
I do not want to change the open source code.
---
### Author:  [@daryldoak](https://forum.liquibase.org/u/daryldoak)
#### Post date: [December 9, 2022, 6:07pm UTC](https://forum.liquibase.org/t/runonchange-true/7617/2 "2022-12-09T18:07:59Z")
runOnChange is a changeset attribute, it cannot be set at the master changelog level.
> **[Changelog Formats](https://docs.liquibase.com/concepts/changelogs/changelog-formats.html)**
>
> Reference information for using changesets in Liquibase. Changesets allow you to group database change types together and is a unit of change that Liquibase executes on a database.
It actually sounds like a bad idea to have every changeset as runOnChange, since many SQL statements are not repeatable (Your mileage may vary depending on your DBMS platform of course).
---
### Author:  [@rajxraj](https://forum.liquibase.org/u/rajxraj)
#### Post date: [December 15, 2022, 9:12pm UTC](https://forum.liquibase.org/t/runonchange-true/7617/3 "2022-12-15T21:12:29Z")
It would be best if you had this at the changeset level for repeatable scripts. I think it is better not to have this setting for any DDL, not recommended. The whole point of liquibase is to skip the changesets that are already applied to your db.