I've noticed that each time a new PR is made, many of the config.h and *.cfg files also get committed/updated.
In a way, I don't see these as "real" commits as they are essentially just configuration files and are specific to a particularly instance of running the code rather than the state of the code as a whole. In this way, I'd suggest we remove these from the repo and add them to the .gitignore so they are not tracked by git but could still be present in your local repo without any issues.
I don't see this is as a problem as the user is always going to generate these, either using the GUI or pydrad, every time they want to run the code. This also eliminates the risk of accidentally using a stale configuration/header file and not realizing it.
I've noticed that each time a new PR is made, many of the
config.hand*.cfgfiles also get committed/updated.In a way, I don't see these as "real" commits as they are essentially just configuration files and are specific to a particularly instance of running the code rather than the state of the code as a whole. In this way, I'd suggest we remove these from the repo and add them to the
.gitignoreso they are not tracked by git but could still be present in your local repo without any issues.I don't see this is as a problem as the user is always going to generate these, either using the GUI or pydrad, every time they want to run the code. This also eliminates the risk of accidentally using a stale configuration/header file and not realizing it.