Merge branch 'mozilla:main' into master

Author: dveditz

.adr-dir

@@ -1 +1 @@
-docs/architecture/decisions
+docs/docs/architecture/decisions

.dockerignore

@@ -2,3 +2,6 @@
 .env
 **/__pycache__
 **/*.pyc
+
+# Ignore generated credentials from google-github-actions/auth
+gha-creds-*.json

.github/CODEOWNERS

@@ -0,0 +1,20 @@
+# See the code-owners Github docs:
+# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+
+# Mostly backend-y directories
+/bedrock @mozilla/bedrock-codeowners-backend
+/docker @mozilla/bedrock-codeowners-backend
+/lib @mozilla/bedrock-codeowners-backend
+/requirements @mozilla/bedrock-codeowners-backend
+/wsgi @mozilla/bedrock-codeowners-backend
+*.py @mozilla/bedrock-codeowners-backend
+
+# Mostly frontend-y directories
+/media @mozilla/bedrock-codeowners-frontend
+/package.json @mozilla/bedrock-codeowners-frontend
+*.html @mozilla/bedrock-codeowners-frontend
+*.js @mozilla/bedrock-codeowners-frontend
+*.scss @mozilla/bedrock-codeowners-frontend
+
+# Top-level /tests are mostly frontend-y
+/tests @mozilla/bedrock-codeowners-frontend

.github/CONTRIBUTING.md

@@ -7,7 +7,7 @@ for development, as well as how to format your code and commit messages.
 Following these guidelines will very much increase the chances of a pleasant
 code-review experience.
 
-[bedrock docs]: http://bedrock.readthedocs.org/en/latest/contribute.html
+[bedrock docs]: https://mozmeao.github.io/platform-docs/contribute/
 
 ## How to Get Started
 
@@ -16,7 +16,7 @@ If this is your first time contributing then we suggest you first
 a little. This will help you familiarize yourself with the layout of files and
 how they relate to different pages of the website.
 
-[install bedrock]: https://bedrock.readthedocs.io/en/latest/install.html#installing-bedrock
+[install bedrock]: https://mozmeao.github.io/platform-docs/install/
 
 ## Finding an Issue to Work On
 

.github/ISSUE_TEMPLATE/bug_report.md

@@ -2,7 +2,7 @@
 name: "Bug Report \U0001F41B"
 about: Something isn't working as expected? Here is the right place to report.
 title: ''
-labels: 'Bug :bug:'
+labels: 'Bug'
 assignees: ''
 
 ---

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,8 +1,8 @@
-## One-line summary
+_If this changeset needs to go into the FXC codebase, please add the `WMO and FXC` label._
 
 
+## One-line summary
 
-- [ ] I used an AI to write some of this code.
 
 ## Significant changes and points to review
 

.github/actions/slack/action.yaml

@@ -9,12 +9,23 @@ inputs:
   env_name:
     description: Name of env involved - one of dev, test, stage or prod
     required: true
+    type: choice
+    options:
+      - dev
+      - test
+      - stage
+      - prod
   label:
     description: Very brief summary of what this notification is for - e.g. 'Integration tests'
     required: true
   status:
     description: Status of message type to be sent, supported values 'info', 'success', 'failure'
     required: true
+    type: choice
+    options:
+      - info
+      - success
+      - failure
   channel_id:
     description: Slack channel id to send messages
     required: true
@@ -39,8 +50,10 @@ runs:
   steps:
     - id: set-build-status-color
       shell: bash
+      env:
+        STATUS: ${{ inputs.status }}
       run: >-
-        eval "case ${{ inputs.status }} in
+        eval "case $STATUS in
             info)
                 echo 'STATUS_COLOR=#00FFFF';;
             success)

.github/copilot-instructions.md

@@ -0,0 +1,100 @@
+# Review guidelines for Github Copilot
+
+When reviewing code:
+
+Fetch the latest version of all the checklists mentioned on https://mozmeao.github.io/platform-docs/code-review/checklists/ - use these as a guide to our project best practices. You may cache these for up to three days at a time.
+
+Try to use Conventional Comments to indicate the kind of feedback you are providing, and whether it's blocking or non-blocking.
+
+Areas to consider when reviewing:
+
+## 1. Correctness & Safety
+
+* Potential bugs, edge cases, or incorrect assumptions
+
+* Error handling (especially around I/O, network calls, and external services)
+
+* Race conditions, concurrency issues, or state inconsistencies
+
+* Security concerns (e.g., injection risks, unsafe deserialization, secrets handling)
+
+Heavily flag changes that add risks to uptime or functionality that do not appear to have been considered in the changeset.
+Be particularly aware of CMS-backed content that is not richtext. Ensure it's escaped properly when used in templates.
+
+
+## 2. Design & Architecture
+
+* Is the code structured in a way that will scale and be maintainable?
+
+* Are responsibilities clearly separated?
+
+* Are abstractions appropriate, or is the code over/under-engineered?
+
+* Does this change align with existing patterns in the codebase?
+
+
+## 3. Readability & Intent
+
+* Is the intent of the code obvious to a future reader?
+
+* Are names (variables, functions, classes) clear and meaningful?
+
+* Would a short comment help explain _why_ something is done (not _what_)?
+
+
+## 4. Tests
+
+* Are new behaviors adequately covered by tests?
+
+* Do tests clearly express intent?
+
+* Are edge cases tested where appropriate?
+
+* Flag missing tests, but don’t require tests for trivial changes
+
+
+## 5. Performance (When Relevant)
+
+* Call out obvious inefficiencies or unnecessary work
+
+* Avoid premature optimization
+
+* Note performance implications only if they are meaningful in context
+
+## 6. Localization (L10N)
+
+* If new strings are added to the codebase that are not marked up as Fluent strings, add a non-blocking comment questioning whether they need to be translated or are OK in just one language.
+
+
+# What Not to Do
+
+* Do not restate what the code already clearly shows
+
+* Do not suggest large refactors unless there is a clear payoff
+
+* Do not enforce personal style preferences
+
+* Do not block on formatting issues that can be handled by linters or formatters
+
+# How to Write Comments
+
+* Be concise and specific
+
+* Use Conventional Comments to hint what the feedback is
+
+* Prefer “Consider…” or “What do you think about…” over “This is wrong”
+
+* When suggesting a change, always explain _why_ it improves the code
+
+* Use code snippets in suggestions when helpful and would change less than 10 lines of code.
+
+
+# Overall Review Summary
+
+When appropriate, provide a short summary comment that answers:
+
+* Is this change safe to merge?
+
+* What are the main risks (if any)?
+
+* Are there follow-ups worth tracking separately?

.github/dependabot.yml

@@ -19,6 +19,8 @@ updates:
       - dependency-name: '@mozmeao/cookie-helper'
       - dependency-name: '@mozmeao/dnt-helper'
       - dependency-name: '@mozmeao/trafficcop'
+      # Pin sass at 1.91.0 until mozilla/protocol#982
+      - dependency-name: 'sass'
       # Need to be kept in sync with pre-commit-config.yaml.
       - dependency-name: 'eslint'
       - dependency-name: 'eslint-config-prettier'

.github/l10n/check_toml_configs.py

@@ -0,0 +1,45 @@
+#!/usr/bin/env python
+
+# This Source Code Form is subject to the terms of the Mozilla Public
+# License, v. 2.0. If a copy of the MPL was not distributed with this
+# file, You can obtain one at https://mozilla.org/MPL/2.0/.
+
+import argparse
+import os
+import sys
+from pathlib import Path
+
+from moz.l10n.paths import L10nConfigPaths
+
+
+def main():
+    parser = argparse.ArgumentParser()
+    parser.add_argument("--path", dest="repo_path", help="Path to repository clone", required=True)
+    args = parser.parse_args()
+
+    # Find all TOML files in l10n/configs
+    repo_path = args.repo_path
+    config_path = Path(os.path.join(repo_path, "l10n", "configs"))
+    config_files = list(config_path.glob("*.toml"))
+
+    errors = []
+    for config in config_files:
+        toml_path = os.path.join(repo_path, config)
+        project_config_paths = L10nConfigPaths(toml_path)
+        reference_files = [os.path.abspath(ref_path) for ref_path in project_config_paths.ref_paths]
+
+        for file in reference_files:
+            if not os.path.exists(file):
+                errors.append(f"[{config}] {os.path.relpath(file, repo_path)}")
+
+    if errors:
+        print("Missing reference files:")
+        for error in errors:
+            print(f"  {error}")
+        sys.exit(1)
+    else:
+        print("No missing reference files.")
+
+
+if __name__ == "__main__":
+    main()