.gitignore

# Please! We need to manage git ignore file so it will contain a minimal set of non-nonsense entries.
# Such minimal and precise exclusion list help reveal misbehaving / misconfigured tools
# and scripts, instead of blindly sweep problems under the rug.
#
# When adding entries here, please, do your best to briefly specify:
# * Which program generates or uses this kind of files or folders
# * Why these files are kept out of the repo
# * Be precise about directories by placing leading / trailing slash where needed
#
# Quick reference on slashes:
# - Having a slash in front means that exclusion will only work on the top/root level
# of the repo. Otherwise we will ignore entries at arbitrary level of nesting.
# - Having a trailing slash means that exclusion will work only on directories.

# Executions of ad-hoc scripts and binaries allowed to create various temporary
# logs or stdout/stderr dumps in working directories
# We exclude them and ask to stick to this convention of using these filename extensions:
*.out
*.err
*.log

# JVM specific dumps and crash reports
# TODO add threaddump / crash dump filenames/extensions
*.hprof

# Folders for placing downloaded or generated tools, scripts or repos
# which are not part of the hermetic CI build.
# Can be present on different levels of nesting
.ext/

# Buck (or other tools) local config customizations
# Manually created to override main config, local and specific to a user
# Should be managed / backed up manually and outside ot the repo
*.local

# Buck directories for daemon and build output
# Auto created when running builds, present only in root
/.buckd/
/buck-out/

# Maven output directory and generated files in case we run some maven commands
target/
pom.xml

# Symlinks for downloaded/output jars and generated source folders
# for convenience of IDEs and ad-hoc tools.
# Created in the directories along BUCK files containing
# remote_file/java_binary rules which produce local jar files.
# Regenerated by calling `node up --lib --intellij`
.out/
*-gen
*-gen[1234]

# Project files can be regenerated `node up --intellij --eclipse`
# Can be present on different levels of nesting.

# Jetbrains Intellij IDEA project and module files,
.idea/
*.iml

# Eclipse project and module definitions
.ecj/
.classes/
.test-classes/
.settings/
.factorypath
.classpath
.project
.externalToolBuilders

VSCode settings
.vscode/

# Symlink for experimenting with local highlands,
# usually bypassing remote version ./ext/highlands/
/.highlands

# MacOS custom file/folder attributes, irrelevant to the repo
.DS_Store