Add gitignore template for Automation Studio 4 Projects #4424
There are no files selected for viewing
|
There was a problem hiding this comment. I did some checking around and I'm not sure Autmoation Studio quite reaches the degree of widespread use and popularity we're looking for to be included in our root. Would you be willing to move it to the community folder? There was a problem hiding this comment. Is there data I could provide that might be useful in that decision? Otherwise I defer to you on what would be most appropriate. According to B&R, Automation Studio has programmed machines for 30,000 factories worldwide, and is used by about 4,000 machine builders worldwide. They are unique in the industrial automation space as their PLC code is stored in plaintext, and can be effectively used with source control. I know it might be surprising to hear that as a unique metric, but it is. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,31 @@ | ||
| # gitignore template for B&R Automation Studio (AS) 4 | ||
| # website: https://www.br-automation.com/en-us/products/software/automation-software/automation-studio/ | ||
|
|
||
| # AS temporary directories | ||
| Binaries/ | ||
| Diagnosis/ | ||
| Temp/ | ||
| TempObjects/ | ||
|
|
||
| # AS transfer files | ||
| *artransfer.br | ||
| *arTrsfmode.nv | ||
|
|
||
| # 'ignored' directory | ||
| ignored/ | ||
|
|
||
| # ARNC0ext | ||
| *arnc0ext.br | ||
|
|
||
| # AS File types | ||
| *.bak | ||
| *.isopen | ||
| *.orig | ||
| *.log | ||
| *.asar | ||
| *.csvlog* | ||
| *.set | ||
| !**/Physical/**/*.set | ||
|
|
||
| # RevInfo variables | ||
| *RevInfo.var |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't accept template files for specific versions in the root. Please see our docs for more details and adjust accordingly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To clarify, this version number is not for the .gitignore template itself, but is referencing a specific Automation Studio version. An existing .gitignore template for automation software, TwinCAT3, follows this format.
Would it still be best to remove the version number from the filename?
More context: I'm not sure which would be most appropriate as "current supported version." Automation Studio 4 was released in 2013 and is the current standard. But later this year, Automation Studio 6 will be released (5 was skipped) so this distinction seemed useful, as I'm unsure if there will be similarities with regards to gitignore. The automation space moves somewhat slowly, so most users will still be using version 4 for years to come, because so many machines were developed with it and it is more proven.