build: more setup

Author: longlho

.bazelignore

@@ -1 +1,5 @@
-e2e/
+# Examples and e2e tests have their own MODULE.bazel files and are tested separately in CI
+# The REPO.bazel files mark them as separate repos, but we also need .bazelignore
+# to prevent //... from traversing into them
+examples
+e2e

.bcr/metadata.template.json

@@ -1,7 +1,7 @@
 {
-  "homepage": "https://github.com/myorg/rules_mylang",
+  "homepage": "https://github.com/formatjs/rules_formatjs",
   "maintainers": [],
-  "repository": ["github:myorg/rules_mylang"],
+  "repository": ["github:formatjs/rules_formatjs"],
   "versions": [],
   "yanked_versions": {}
 }

.gitattributes

@@ -8,4 +8,4 @@ examples export-ignore
 
 # Occasionally there's a need to "stamp" the release version into a file
 # See https://blog.aspect.build/releasing-bazel-rulesets-rust for details if you need this.
-# mylang/version.bzl export-subst
+# formatjs/version.bzl export-subst

.github/workflows/buildifier.yaml

@@ -13,5 +13,8 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v5
+      - uses: bazel-contrib/setup-bazel@0.16.0
+        with:
+          bazelisk-cache: true
       - name: buildifier
         run: bazel run --enable_bzlmod //.github/workflows:buildifier.check

.github/workflows/ci.yaml

@@ -1,52 +1,49 @@
 name: CI
-# Controls when the action will run.
 on:
-  # Triggers the workflow on push or pull request events but only for the main branch
   push:
     branches: [main]
   pull_request:
     branches: [main]
-  # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:
 concurrency:
-  # Cancel previous actions from the same PR or branch except 'main' branch.
-  # See https://docs.github.com/en/actions/using-jobs/using-concurrency and https://docs.github.com/en/actions/learn-github-actions/contexts for more info.
-  group: concurrency-group::${{ github.workflow }}::${{ github.event.pull_request.number > 0 && format('pr-{0}', github.event.pull_request.number) || github.ref_name }}${{ github.ref_name == 'main' && format('::{0}', github.run_id) || ''}}
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
   cancel-in-progress: ${{ github.ref_name != 'main' }}
 jobs:
   test:
-    uses: bazel-contrib/.github/.github/workflows/bazel.yaml@v6
-    with:
-      folders: |
-        [
-          ".",
-          "e2e/smoke"
-        ]
-      exclude: |
-        [
-          {"folder": ".", "bzlmodEnabled": false},
-          {"folder": ".", "bazelVersion": "6.4.0"}
-        ]
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        folder:
+          - "."
+          - "e2e/smoke"
+          - "examples/simple"
+          - "examples/aggregate"
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v5
+      - uses: bazel-contrib/setup-bazel@0.16.0
+        with:
+          bazelisk-cache: true
+      - name: Test ${{ matrix.folder }}
+        working-directory: ${{ matrix.folder }}
+        run: bazel test //...
+
   pre-commit:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v5
       - uses: pre-commit/action@v3.0.1
-  # For branch protection settings, this job provides a "stable" name that can be used to gate PR merges
-  # on "all matrix jobs were successful".
+
   conclusion:
     needs: [test, pre-commit]
     runs-on: ubuntu-latest
     if: always()
     steps:
       - uses: technote-space/workflow-conclusion-action@45ce8e0eb155657ab8ccf346ade734257fd196a5 # v3.0.3
-      # Note: possible conclusion values:
-      # https://github.com/technote-space/workflow-conclusion-action/blob/main/src/constant.ts
-      - name: report success
+      - name: Report success
         if: ${{ env.WORKFLOW_CONCLUSION == 'success' }}
-        working-directory: /tmp
-        run: echo ${{ env.WORKFLOW_CONCLUSION }} && exit 0
-      - name: report failure
+        run: exit 0
+      - name: Report failure
         if: ${{ env.WORKFLOW_CONCLUSION == 'failure' }}
-        working-directory: /tmp
-        run: echo ${{ env.WORKFLOW_CONCLUSION }} && exit 1
+        run: exit 1

.github/workflows/release.yaml

@@ -22,7 +22,7 @@ jobs:
   release:
     uses: bazel-contrib/.github/.github/workflows/release_ruleset.yaml@v7.2.2
     with:
-      release_files: rules_mylang-*.tar.gz
+      release_files: rules_formatjs-*.tar.gz
       prerelease: false
       tag_name: ${{ inputs.tag_name || github.ref_name }}
   publish:

.github/workflows/release_prep.sh

@@ -8,8 +8,8 @@ TAG=$1
 # The prefix is chosen to match what GitHub generates for source archives
 # This guarantees that users can easily switch from a released artifact to a source archive
 # with minimal differences in their code (e.g. strip_prefix remains the same)
-PREFIX="rules_mylang-${TAG:1}"
-ARCHIVE="rules_mylang-$TAG.tar.gz"
+PREFIX="rules_formatjs-${TAG:1}"
+ARCHIVE="rules_formatjs-$TAG.tar.gz"
 
 # NB: configuration for 'git archive' is in /.gitattributes
 git archive --format=tar --prefix=${PREFIX}/ ${TAG} | gzip > $ARCHIVE
@@ -30,7 +30,7 @@ cat << EOF
 2. Add to your \`MODULE.bazel\` file:
 
 \`\`\`starlark
-bazel_dep(name = "com_myorg_rules_mylang", version = "${TAG:1}")
+bazel_dep(name = "rules_formatjs", version = "${TAG:1}")
 \`\`\`
 
 ## Using WORKSPACE
@@ -40,10 +40,10 @@ Paste this snippet into your \`WORKSPACE.bazel\` file:
 \`\`\`starlark
 load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
 http_archive(
-    name = "com_myorg_rules_mylang",
+    name = "rules_formatjs",
     sha256 = "${SHA}",
     strip_prefix = "${PREFIX}",
-    url = "https://github.com/myorg/rules_mylang/releases/download/${TAG}/${ARCHIVE}",
+    url = "https://github.com/formatjs/rules_formatjs/releases/download/${TAG}/${ARCHIVE}",
 )
 EOF
 

CONTRIBUTING.md

@@ -28,19 +28,19 @@ Run `bazel run //:gazelle` to keep them up-to-date.
 ## Using this as a development dependency of other rules
 
 You'll commonly find that you develop in another WORKSPACE, such as
-some other ruleset that depends on rules_mylang, or in a nested
+some other ruleset that depends on rules_formatjs, or in a nested
 WORKSPACE in the integration_tests folder.
 
 To always tell Bazel to use this directory rather than some release
 artifact or a version fetched from the internet, run this from this
 directory:
 
 ```sh
-OVERRIDE="--override_repository=rules_mylang=$(pwd)/rules_mylang"
+OVERRIDE="--override_repository=rules_formatjs=$(pwd)"
 echo "common $OVERRIDE" >> ~/.bazelrc
 ```
 
-This means that any usage of `@rules_mylang` on your system will point to this folder.
+This means that any usage of `@rules_formatjs` on your system will point to this folder.
 
 ## Releasing
 
@@ -51,7 +51,7 @@ If you do nothing, eventually the newest commits will be released automatically
 This automation is defined in .github/workflows/tag.yaml.
 
 Rather than wait for the cron event, you can trigger manually. Navigate to
-https://github.com/myorg/rules_mylang/actions/workflows/tag.yaml
+https://github.com/formatjs/rules_formatjs/actions/workflows/tag.yaml
 and press the "Run workflow" button.
 
 If you need control over the next release version, for example when making a release candidate for a new major,

MODULE.bazel

@@ -43,10 +43,3 @@ bazel_dep(name = "bazel_lib", version = "3.0.0", dev_dependency = True)
 bazel_dep(name = "buildifier_prebuilt", version = "8.2.1", dev_dependency = True)
 
 bazel_dep(name = "bazelrc-preset.bzl", version = "1.6.0")
-
-# FormatJS CLI toolchain
-formatjs_cli = use_extension("//formatjs_cli:extensions.bzl", "formatjs_cli")
-formatjs_cli.toolchain(version = "0.1.0")
-use_repo(formatjs_cli, "formatjs_cli_toolchains")
-
-register_toolchains("@formatjs_cli_toolchains//:all")