Move google tag into a partial (#3836)

com-lihaoyi · Oct 24, 2024 · ee116b0 · ee116b0
1 parent bbb6fcd
commit ee116b0
Show file tree

Hide file tree

Showing 57 changed files with 99 additions and 154 deletions.
diff --git a/docs/modules/ROOT/pages/comparisons/gradle.adoc b/docs/modules/ROOT/pages/comparisons/gradle.adoc
@@ -1,11 +1,7 @@
 = Case Study: Mill vs Gradle
 :page-aliases: Case_Study_Mill_vs_Gradle.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 This page compares using Mill to Gradle, using the https://github.com/mockito/mockito[Mockito Testing Library]
 codebase as the example. Mockito is a medium sized codebase, 100,000 lines of Java split over 22

diff --git a/docs/modules/ROOT/pages/comparisons/maven.adoc b/docs/modules/ROOT/pages/comparisons/maven.adoc
@@ -1,11 +1,7 @@
 = Case Study: Mill vs Maven
 :page-aliases: Case_Study_Mill_vs_Maven.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 This page compares using Mill to Maven, using the https://github.com/netty/netty[Netty Network Server]
 codebase as the example. Netty is a large, old codebase. 500,000 lines of Java, written by

diff --git a/docs/modules/ROOT/pages/comparisons/sbt.adoc b/docs/modules/ROOT/pages/comparisons/sbt.adoc
@@ -1,11 +1,7 @@
 = Case Study: Mill vs SBT
 :page-aliases: Case_Study_Mill_vs_SBT.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 This page compares using Mill to SBT, using the https://github.com/gatling/gatling[Gatling Load Testing Framework]
 codebase as the example. Gatling is a medium sized codebase, 40,000 lines of Scala split over 21

diff --git a/docs/modules/ROOT/pages/depth/design-principles.adoc b/docs/modules/ROOT/pages/depth/design-principles.adoc
@@ -1,6 +1,7 @@
 = Mill Design Principles
 :page-aliases: Mill_Internals.adoc, Mill_Design_Principles.adoc
 
+include::partial$gtag-config.adoc[]
 
 The following external resources give more of a flavor of the architecture behind
 Mill:

diff --git a/docs/modules/ROOT/pages/depth/evaluation-model.adoc b/docs/modules/ROOT/pages/depth/evaluation-model.adoc
@@ -1,6 +1,8 @@
 = The Mill Evaluation Model
 :page-aliases: The_Mill_Evaluation_Model.adoc
 
+include::partial$gtag-config.adoc[]
+
 Evaluating a Mill task typically goes through the following phases:
 
 1. *Compilation*: Mill compiles the `build.mill` to classfiles, following the

diff --git a/docs/modules/ROOT/pages/depth/large-builds.adoc b/docs/modules/ROOT/pages/depth/large-builds.adoc
@@ -1,6 +1,8 @@
 = Large Builds and Monorepos
 :page-aliases: Structuring_Large_Builds.adoc
 
+include::partial$gtag-config.adoc[]
+
 This section walks through Mill features and techniques used for managing large builds.
 While Mill works great for small single-module projects, it is also able to work
 effectively with large projects with hundreds of modules. Mill's own build for the

diff --git a/docs/modules/ROOT/pages/depth/sandboxing.adoc b/docs/modules/ROOT/pages/depth/sandboxing.adoc
@@ -1,6 +1,8 @@
 = Mill Sandboxing
 :page-aliases: Mill_Sandboxing.adoc
 
+include::partial$gtag-config.adoc[]
+
 == Task Sandboxing
 
 include::partial$example/depth/sandbox/1-task.adoc[]

diff --git a/docs/modules/ROOT/pages/depth/why-scala.adoc b/docs/modules/ROOT/pages/depth/why-scala.adoc
@@ -1,5 +1,7 @@
 = Why does Mill use Scala?
 
+include::partial$gtag-config.adoc[]
+
 One question that comes up a lot among Mill users is why use Scala as the language
 to configure your build? Why not YAML, XML, TOML, Bash, Groovy, Python, Java, or any of the
 other hundred programming and configuration languages in widespread use today? Scala

diff --git a/docs/modules/ROOT/pages/extending/contrib-plugins.adoc b/docs/modules/ROOT/pages/extending/contrib-plugins.adoc
@@ -1,6 +1,7 @@
 = Contrib Plugins
 :page-aliases: Contrib_Plugins.adoc, Contrib_Modules.adoc
 
+include::partial$gtag-config.adoc[]
 
 The ((plugins)) in this section are hosted in the Mill git tree and developed / maintained by the community.
 

diff --git a/docs/modules/ROOT/pages/extending/import-ivy-plugins.adoc b/docs/modules/ROOT/pages/extending/import-ivy-plugins.adoc
@@ -1,6 +1,8 @@
 = Import Libraries and Plugins
 :page-aliases: Import_File_And_Import_Ivy.adoc, Using_Plugins.adoc
 
+include::partial$gtag-config.adoc[]
+
 This page illustrates usage of  `import $ivy`.
 `import $ivy` lets you import JVM dependencies into your `build.mill`, so
 you can use arbitrary third-party libraries at build-time. This makes

diff --git a/docs/modules/ROOT/pages/extending/meta-build.adoc b/docs/modules/ROOT/pages/extending/meta-build.adoc
@@ -1,6 +1,8 @@
 = The Mill Meta-Build
 :page-aliases: The_Mill_Meta_Build.adoc
 
+include::partial$gtag-config.adoc[]
+
 The meta-build manages the compilation of the `build.mill`.
 Customizing the meta-build gives you greater control over how exactly your
 `build.mill` evaluates.

diff --git a/docs/modules/ROOT/pages/extending/new-language.adoc b/docs/modules/ROOT/pages/extending/new-language.adoc
@@ -1,5 +1,7 @@
 = Support for New Languages
 
+include::partial$gtag-config.adoc[]
+
 This section walks through the process of adding support for a new programming
 language to Mill. We will be adding a small `trait TypeScriptModule` with the
 ability to resolve dependencies, typecheck local code, and optimize a final

diff --git a/docs/modules/ROOT/pages/extending/running-jvm-code.adoc b/docs/modules/ROOT/pages/extending/running-jvm-code.adoc
@@ -1,5 +1,7 @@
 = Running Dynamic JVM Code
 
+include::partial$gtag-config.adoc[]
+
 While xref:extending/import-ivy-plugins.adoc[import $ivy] is convenient,
 it comes with limitations as the JVM library it imports is global to your build:
 

diff --git a/docs/modules/ROOT/pages/extending/thirdparty-plugins.adoc b/docs/modules/ROOT/pages/extending/thirdparty-plugins.adoc
@@ -1,6 +1,8 @@
 = Third-Party Plugins
 :page-aliases: Thirdparty_Modules.adoc, Thirdparty_Plugins.adoc
 
+include::partial$gtag-config.adoc[]
+
 The Plugins in this section are developed/maintained outside the mill git tree.
 This list is most likely not complete.
 If you wrote a Mill plugin or find that one is missing in this list, please open a {mill-github-url}/pulls[pull request] and add that plugin with a short description (in alphabetical order).

diff --git a/docs/modules/ROOT/pages/extending/writing-plugins.adoc b/docs/modules/ROOT/pages/extending/writing-plugins.adoc
@@ -1,4 +1,6 @@
 = Writing Mill Plugins
 :page-aliases: Writing_Mill_Plugins.adoc
 
+include::partial$gtag-config.adoc[]
+
 include::partial$example/extending/plugins/7-writing-mill-plugins.adoc[]
diff --git a/docs/modules/ROOT/pages/fundamentals/bundled-libraries.adoc b/docs/modules/ROOT/pages/fundamentals/bundled-libraries.adoc
@@ -1,6 +1,8 @@
 = Bundled Libraries
 :page-aliases: External_References.adoc, Bundled_Libraries.adoc
 
+include::partial$gtag-config.adoc[]
+
 Mill comes bundled with a set of external Open Source libraries and projects.
 
 == OS-lib

diff --git a/docs/modules/ROOT/pages/fundamentals/cross-builds.adoc b/docs/modules/ROOT/pages/fundamentals/cross-builds.adoc
@@ -1,6 +1,8 @@
 = Cross Builds
 :page-aliases: Cross_Builds.adoc
 
+include::partial$gtag-config.adoc[]
+
 Cross-building refers to taking the same sources and configuration and building
 it multiple times with minor changes. This could mean taking the same Scala
 codebase and building it across multiple Scala versions, taking the same

diff --git a/docs/modules/ROOT/pages/fundamentals/library-deps.adoc b/docs/modules/ROOT/pages/fundamentals/library-deps.adoc
@@ -3,6 +3,8 @@
 :link-coursier-doc: https://get-coursier.io/docs/overview
 :page-aliases: Library_Dependencies.adoc
 
+include::partial$gtag-config.adoc[]
+
 Beside the dependencies between Mill modules, most non-trivial source projects have dependencies to other libraries.
 
 Mill uses {link-coursier}[coursier] to resolve and download dependencies.

diff --git a/docs/modules/ROOT/pages/fundamentals/modules.adoc b/docs/modules/ROOT/pages/fundamentals/modules.adoc
@@ -1,6 +1,8 @@
 = Modules
 :page-aliases: Modules.adoc
 
+include::partial$gtag-config.adoc[]
+
 `mill.Module` serves two main purposes:
 
 1. As ``object``s, they serve as namespaces that let you group related ``Task``s

diff --git a/docs/modules/ROOT/pages/fundamentals/out-dir.adoc b/docs/modules/ROOT/pages/fundamentals/out-dir.adoc
@@ -1,6 +1,8 @@
 = The Output Directory
 :page-aliases: Out_Dir.adoc
 
+include::partial$gtag-config.adoc[]
+
 Mill puts all its output in the top-level `out/` folder.
 
 == Structure of the `out/` Directory

diff --git a/docs/modules/ROOT/pages/fundamentals/query-syntax.adoc b/docs/modules/ROOT/pages/fundamentals/query-syntax.adoc
@@ -1,6 +1,8 @@
 = Task Query Syntax
 :page-aliases: Task_Query_Syntax.adoc
 
+include::partial$gtag-config.adoc[]
+
 When interacting with Mill from the CLI, you often need to select tasks or modules.
 In most places, where Mill accepts a task, it really accepts a task selector query, which is the name of a task in its simplest form, but it can also contain wildcards, type pattern and other special syntax, making it a powerful tool to select specific tasks.
 

diff --git a/docs/modules/ROOT/pages/fundamentals/tasks.adoc b/docs/modules/ROOT/pages/fundamentals/tasks.adoc
@@ -1,6 +1,8 @@
 = Tasks
 :page-aliases: Tasks.adoc
 
+include::partial$gtag-config.adoc[]
+
 One of Mill's core abstractions is its _Task Graph_: this is how Mill defines,
 orders and caches work it needs to do, and exists independently of any support
 for building Java, Kotlin, or Scala.

diff --git a/docs/modules/ROOT/pages/javalib/android-examples.adoc b/docs/modules/ROOT/pages/javalib/android-examples.adoc
@@ -1,11 +1,7 @@
 = (Experimental) Android Builds
 :page-aliases: android_app_examples.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 This page provides an example of using Mill as a build tool for Android applications.
 This workflow is still pretty rough and nowhere near production ready, but can serve as

diff --git a/docs/modules/ROOT/pages/javalib/build-examples.adoc b/docs/modules/ROOT/pages/javalib/build-examples.adoc
@@ -1,11 +1,7 @@
 = Java Build Examples
 :page-aliases: Java_Build_Examples.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 On this page, we will explore the Mill build tool via a series of simple Java
 example projects.

diff --git a/docs/modules/ROOT/pages/javalib/builtin-commands.adoc b/docs/modules/ROOT/pages/javalib/builtin-commands.adoc
@@ -1,8 +1,11 @@
 = Built-in Commands
 :page-aliases: Java_Builtin_Commands.adoc
 
+include::partial$gtag-config.adoc[]
+
 :language: Java
 :language-small: java
 
 
+
 include::partial$example/javalib/basic/5-builtin-commands.adoc[]
diff --git a/docs/modules/ROOT/pages/javalib/dependencies.adoc b/docs/modules/ROOT/pages/javalib/dependencies.adoc
@@ -1,10 +1,6 @@
 = Java Library Dependencies
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 This page goes into more detail about configuring third party dependencies
 for `JavaModule`.

diff --git a/docs/modules/ROOT/pages/javalib/installation-ide.adoc b/docs/modules/ROOT/pages/javalib/installation-ide.adoc
@@ -1,6 +1,8 @@
 = Installation and IDE Support
 :page-aliases: Java_Installation_IDE_Support.adoc
 
+include::partial$gtag-config.adoc[]
+
 :language: Java
 :language-small: java
 

diff --git a/docs/modules/ROOT/pages/javalib/intro.adoc b/docs/modules/ROOT/pages/javalib/intro.adoc
@@ -15,11 +15,7 @@
 = Building Java Projects with Mill
 :page-aliases: index.adoc, Intro_to_Mill.adoc, Intro_to_Mill_for_Java.adoc, Java_Intro_to_Mill.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 
 :language: Java

diff --git a/docs/modules/ROOT/pages/javalib/linting.adoc b/docs/modules/ROOT/pages/javalib/linting.adoc
@@ -1,11 +1,7 @@
 = Linting Java Projects
 :page-aliases: Linting_Java_Projects.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 This page will discuss common topics around enforcing the code quality of Java
 codebases using the Mill build tool

diff --git a/docs/modules/ROOT/pages/javalib/module-config.adoc b/docs/modules/ROOT/pages/javalib/module-config.adoc
@@ -1,11 +1,7 @@
 = Java Module Configuration
 :page-aliases: Java_Module_Config.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 :language: Java
 :language-small: java

diff --git a/docs/modules/ROOT/pages/javalib/publishing.adoc b/docs/modules/ROOT/pages/javalib/publishing.adoc
@@ -1,11 +1,7 @@
 = Publishing Java Projects
 :page-aliases: Publishing_Java_Projects.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 This page will discuss common topics around publishing your Java projects for others to use
 

diff --git a/docs/modules/ROOT/pages/javalib/testing.adoc b/docs/modules/ROOT/pages/javalib/testing.adoc
@@ -1,11 +1,7 @@
 = Testing Java Projects
 :page-aliases: Testing_Java_Projects.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 This page will discuss common topics around working with test suites using the Mill build tool
 

diff --git a/docs/modules/ROOT/pages/javalib/web-examples.adoc b/docs/modules/ROOT/pages/javalib/web-examples.adoc
@@ -1,11 +1,7 @@
 = Java Web Examples
 :page-aliases: Java_Web_Examples.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 This page contains examples of using Mill as a build tool for web-applications.
 It covers setting up a basic backend server with a variety of server frameworks

diff --git a/docs/modules/ROOT/pages/kotlinlib/android-examples.adoc b/docs/modules/ROOT/pages/kotlinlib/android-examples.adoc
@@ -1,11 +1,7 @@
 = (Experimental) Android Builds
 :page-aliases: android_app_kotlin_examples.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 This page provides an example of using Mill as a build tool for Android applications.
 This workflow is still pretty rough and nowhere near production ready, but can serve as

diff --git a/docs/modules/ROOT/pages/kotlinlib/build-examples.adoc b/docs/modules/ROOT/pages/kotlinlib/build-examples.adoc
@@ -1,11 +1,7 @@
 = Kotlin Build Examples
 :page-aliases: Kotlin_Build_Examples.adoc
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 On this page, we will explore the Mill build tool via a series of simple Kotlin
 example projects.

diff --git a/docs/modules/ROOT/pages/kotlinlib/builtin-commands.adoc b/docs/modules/ROOT/pages/kotlinlib/builtin-commands.adoc
@@ -1,6 +1,8 @@
 = Built-in Commands
 :page-aliases: Kotlin_Builtin_Commands.adoc
 
+include::partial$gtag-config.adoc[]
+
 :language: Kotlin
 :language-small: kotlin
 

diff --git a/docs/modules/ROOT/pages/kotlinlib/dependencies.adoc b/docs/modules/ROOT/pages/kotlinlib/dependencies.adoc
@@ -1,10 +1,6 @@
 = Kotlin Library Dependencies
 
-++++
-<script>
-gtag('config', 'AW-16649289906');
-</script>
-++++
+include::partial$gtag-config.adoc[]
 
 This page goes into more detail about the various configuration options
 for `KotlinModule`.

diff --git a/docs/modules/ROOT/pages/kotlinlib/installation-ide.adoc b/docs/modules/ROOT/pages/kotlinlib/installation-ide.adoc
@@ -1,5 +1,7 @@
 = Installation and IDE Support
 
+include::partial$gtag-config.adoc[]
+
 :language: Kotlin
 :language-small: kotlin