-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated Files Are Not Gitignored In Some Generators #187
Comments
I was going through the documentation and came across this while running the LDO generator. |
@harshkhandeparkar Sure! you can work on fixing this issue. |
I also found that some generated files which were not gitignored are tracked. Should I also untrack these files? Example: Generated verilog files in ldo-gen and dcdc-gen |
@lulu9312 can you check if we need to prevent these files from version control? |
@harshkhandeparkar I don't think excluding the folders and files you mentioned is a good idea. Intended users are designers and as far as I know, usually they want these files under version control |
@saicharan0112 The folders that are generated such as logs/ results/ will change everytime the generator is run. So I think those files should not be pushed to github because anyway when running the flow again the files will be created again. |
There are templates (which are pushed) for generating these files and they are generated everytime the generator is run and change slightly depending on the configuration. Also there are nearly a hundred files that are generated so I don't think pushing these is a good idea. |
I really appreciate your interest. Can you look at this issue? It would be really wonderful if you can help with this? #37 |
Generated files such as
.log
,.rpt
,.odb
inflow/
,work/
, andsimulations/run/
are not gitignored for the following generators:simulations/run/
is not gitignored.The text was updated successfully, but these errors were encountered: