Upgrade to Pants 2.15 and to scie-pants (#11)

Author: benjyw

.github/workflows/pants.yaml

@@ -19,20 +19,15 @@ jobs:
     name: Perform CI Checks
     needs: org-check
     runs-on: ubuntu-20.04
-    strategy:
-      matrix:
-        # The python version to run Pants itself on.
-        python-version: [3.9]
     steps:
     - uses: actions/checkout@v3
-    - uses: pantsbuild/actions/init-pants@v2
+    - uses: pantsbuild/actions/init-pants@v4-scie-pants
       # This action bootstraps pants and manages 2-3 GHA caches.
       # See: github.com/pantsbuild/actions/tree/main/init-pants/
       with:
-        pants-python-version: ${{ matrix.python-version }}
-        # cache0 makes it easy to bust the cache if needed
+        # v0 makes it easy to bust the cache if needed
         # just increase the integer to start with a fresh cache
-        gha-cache-key: cache0-py${{ matrix.python-version }}
+        gha-cache-key: v0
         # The go backend doesn't use named caches. See the example-python repo for an example
         # of how to set up this cache.
         named-caches-hash: ""
@@ -49,21 +44,21 @@ jobs:
     - name: Install Go
       uses: actions/setup-go@v2
       with:
-        go-version: 1.17.1
+        go-version: 1.19.5
     - name: Bootstrap Pants
-      run: ./pants --version
+      run: pants --version
     - name: Check Pants config files
-      run: ./pants tailor --check update-build-files --check
+      run: pants tailor --check update-build-files --check
     - name: Lint and compile
-      run: ./pants lint check '::'
+      run: pants lint check '::'
     - name: Test
-      run: ./pants test '::'
+      run: pants test '::'
     - name: Package / Run
       run: |
         # We also smoke test that our release process will work by running `package`.
-        ./pants package ::
-        ./pants run cmd/greeter_en
-        ./pants run cmd/greeter_es
+        pants package ::
+        pants run cmd/greeter_en:
+        pants run cmd/greeter_es:
     - name: Upload Pants log
       uses: actions/upload-artifact@v3
       with:

README.md

@@ -4,28 +4,26 @@ An example repository to demonstrate Pants's experimental Golang support.
 
 See the [Golang blog post](https://blog.pantsbuild.org/golang-support-pants-28/) for some unique
 benefits Pants brings to Golang repositories, and see
-[pantsbuild.org/docs/go-overview](https://www.pantsbuild.org/v2.8/docs/go-overview) for more detailed
+[pantsbuild.org/docs/go-overview](https://www.pantsbuild.org/docs/go-overview) for more detailed
 documentation.
 
 This is only one possible way of laying out your project with Pants. See 
 [pantsbuild.org/docs/source-roots#examples](https://www.pantsbuild.org/docs/source-roots#examples) 
 for some other example layouts.
 
-Note: for now, Pants only supports repositories using a single `go.mod`. Please comment on 
-[#13114](https://github.com/pantsbuild/pants/issues/13114) if you need support for greater 
-than one `go.mod` so that we can prioritize adding support.
-
 # Running Pants
 
-You run Pants goals using the `./pants` wrapper script, which will bootstrap the
-configured version of Pants if necessary.
+You run Pants goals using the `pants` launcher binary, which will bootstrap the
+version of Pants configured for this repo if necessary.
+
+See [here](https://www.pantsbuild.org/docs/installation) for how to install the `pants` binary.
 
 # Goals
 
 Pants commands are called _goals_. You can get a list of goals with
 
 ```
-./pants help goals
+pants help goals
 ```
 
 Most goals take arguments to run on. To run on a single directory, use the directory name with 
@@ -35,19 +33,19 @@ end.
 For example:
 
 ```
-./pants lint cmd: internal::
+pants lint cmd: internal::
 ```
 
 You can run on all changed files:
 
 ```
-./pants --changed-since=HEAD lint
+pants --changed-since=HEAD lint
 ```
 
 You can run on all changed files, and any of their "dependees":
 
 ```
-./pants --changed-since=HEAD --changed-dependees=transitive test
+pants --changed-since=HEAD --changed-dependees=transitive test
 ```
 
 # Example Goals
@@ -57,60 +55,60 @@ Try these out in this repo!
 ## Run Gofmt
 
 ```
-./pants fmt ::  # Format all packages.
-./pants fmt cmd/greeter_en  # Format only this package.
-./pants lint pkg/::  # Check that all packages under `pkg` are formatted.
+pants fmt ::  # Format all packages.
+pants fmt cmd/greeter_en:  # Format only this package.
+pants lint pkg::  # Check that all packages under `pkg` are formatted.
 ```
 
 ## Check compilation
 
 ```
-./pants check ::  # Compile all packages.
-./pants check cmd/greeter_en  # Compile only this package and its transitive dependencies.
+pants check ::  # Compile all packages.
+pants check cmd/greeter_en:  # Compile only this package and its transitive dependencies.
 ```
 
 ## Run tests
 
 ```
-./pants test ::  # Run all tests in the repository.
-./pants test pkg/uuid  # Run all the tests in this package.
-./pants test pkg/uuid -- -run TestGenerateUuid  # Run just this one test.
+pants test ::  # Run all tests in the repository.
+pants test pkg/uuid:  # Run all the tests in this package.
+pants test pkg/uuid: -- -run TestGenerateUuid  # Run just this one test.
 ```
 
 ## Create a binary file
 
 Writes the result to the `dist/` folder.
 
 ```
-./pants package cmd/greeter_en
-./pants package cmd/::  # Create all binaries.
+pants package cmd/greeter_en:
+pants package cmd::  # Create all binaries.
 ```
 
 ## Run a binary
 
 ```
-./pants run cmd/greeter_en
-./pants run cmd/greeter_es -- --help
+pants run cmd/greeter_en:
+pants run cmd/greeter_es: -- --help
 ```
 
 ## Determine dependencies
 
 ```
-./pants dependencies cmd/greeter_en
-./pants dependencies --transitive cmd/greeter_en
+pants dependencies cmd/greeter_en:
+pants dependencies --transitive cmd/greeter_en:
 ```
 
 ## Determine dependees
 
 That is, find what code depends on a particular package(s).
 
 ```
-./pants dependees pkg/uuid
-./pants dependees --transitive pkg/uuid
+pants dependees pkg/uuid:
+pants dependees --transitive pkg/uuid: 
 ```
 
 ## Count lines of code
 
 ```
-./pants count-loc '**/*'
+pants count-loc '**/*'
 ```

cmd/greeter_en/BUILD

@@ -3,10 +3,10 @@
 
 go_package()
 
-# This target allows us to use `./pants run` and `./pants package` on this `main` Go package.
+# This target allows us to use `pants run` and `pants package` on this `main` Go package.
 #
 # You can optionally set the field `output_path="greeter_en"`, for example, for the binary's name
-# to be different when running `./pants package`.
+# to be different when running `pants package`.
 go_binary(
     name="bin",
 )

cmd/greeter_es/BUILD

@@ -3,10 +3,10 @@
 
 go_package()
 
-# This target allows us to use `./pants run` and `./pants package` on this `main` Go package.
+# This target allows us to use `pants run` and `pants package` on this `main` Go package.
 #
 # You can optionally set the field `output_path="greeter_es"`, for example, for the binary's name
-# to be different when running `./pants package`.
+# to be different when running `pants package`.
 go_binary(
     name="bin",
 )