This file contains folders to be excluded for tracking during RPA development using UiPath Studio.
Accidentally tracking these folders have caused issues with changing branches during code development.
The UiPath developer community as of 2024 is in excess of 2 million developers spanning over 43 countries.
UiPath itself has been around for 19 years since 2005.
This submission can potentially help millions of new and existing UiPath developers in their work.
This file contains folders to be excluded for tracking during RPA development using UiPath Studio.
Accidentally tracking these folders have caused issues with changing branches during code development.
The UiPath developer community as of 2024 is in excess of 2 million developers spanning over 43 countries.
UiPath itself has been around for 19 years since 2005.
This submission can potentially help millions of new and existing UiPath developers in their work.
**Reasons for making this change:**
_Allowlisting with .gitignore is a technique for dealing with source trees that can have various different untracked local files such as generated output, packages installed through package managers, “working” files, config for individual developers, etc. Rather than trying to come up with some master list of all possible untracked files and add them to .gitignore, it can be easier to start by ignoring everything and then add specific directories back._
_I think the requirements for software development are changing and there is a need to offer an alternative to the denylist._
- https://jasonstitt.com/gitignore-whitelisting-patterns
- https://github.com/golang/go
Signed-off-by: kuritka <kuritka@gmail.com>
Three new files to ignore for GoHugo repositories:
- `/assets/jsconfig.json` - Quote from [JavaScript Building](https://gohugo.io/hugo-pipes/js/): "Hugo will, by default, generate a assets/jsconfig.json file that maps the imports. This is useful for navigation/intellisense help inside code editors, but if you don’t need/want it, you can turn it off."
- `hugo_stats.json` - Quote from [Post Build Resource Transformations ](https://gohugo.io/news/0.69.0-relnotes/): "The prime current use case for the above is CSS pruning in PostCSS. In simple cases you can use the templates as a base for the content filters, but that has its limitations and can be very hard to setup, especially in themed configurations. So we have added a new writeStats configuration that, when enabled, will write a file named hugo_stats.json to your project root with some aggregated data about the build, e.g. list of HTML entities published, to be used to do CSS pruning."
- `.hugo_build.lock` - Quote from [Fine Grained File Filters ](https://gohugo.io/news/0.89.0-relnotes/): "Hugo now writes an empty file named .hugo_build.lock to the root of the project when building (also when doing hugo new mypost.md and other commands that requires a build). We recommend you just leave this file alone. Put it in .gitignore or similar if you don’t want the file in your source repository."
