Test Update

.git-blame-ignore-revs

@@ -1,3 +1,36 @@
+# all: Prune trailing whitespace.
+dda9b9c6da5d3c31fa8769e581a753e95a270803
+
+# all: Remove the "STATIC" macro and just use "static" instead.
+decf8e6a8bb940d5829ca3296790631fcece7b21
+
+# renesas-ra: Fix spelling mistakes found by codespell.
+b3f2f18f927fa2fad10daf63d8c391331f5edf58
+
+# all: Update Python formatting to ruff-format.
+bbd8760bd9a2302e5abee29db279102bb11d7732
+
+# all: Fix various spelling mistakes found by codespell 2.2.6.
+cf490a70917a1b2d38ba9b58e763e0837d0f7ca7
+
+# all: Fix spelling mistakes based on codespell check.
+b1229efbd1509654dec6053865ab828d769e29db
+
+# top: Update Python formatting to black "2023 stable style".
+8b2748269244304854b3462cb8902952b4dcb892
+
+# all: Reformat remaining C code that doesn't have a space after a comma.
+5b700b0af90591d6b1a2c087bb8de6b7f1bfdd2d
+
+# ports: Reformat more C and Python source code.
+5c32111fa0e31e451b0f1666bdf926be2fdfd82c
+
+# all: Update Python formatting to latest Black version 22.1.0.
+ab2923dfa1174dc177f0a90cb00a7e4ff87958d2
+
+# all: Update Python formatting to latest Black version 21.12b0.
+3770fab33449a5dadf8eb06edfae0767e75320a6
+
 # tools/gen-cpydiff.py: Fix formatting of doc strings for new Black.
 0f78c36c5aa458a954eed39a46942209107a553e
 

.gitattributes

@@ -8,14 +8,17 @@
 
 # These are binary so should never be modified by git.
 *.a binary
+*.ico binary
 *.png binary
 *.jpg binary
 *.dxf binary
 *.mpy binary
+*.der binary
 
 # These should also not be modified by git.
 tests/basics/string_cr_conversion.py -text
 tests/basics/string_crlf_conversion.py -text
+tests/micropython/test_normalize_newlines.py.exp -text
 ports/stm32/pybcdc.inf_template -text
 ports/stm32/usbhost/** -text
 ports/cc3200/hal/aes.c -text

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,109 @@
+name: Bug report
+description: Report a bug or unexpected behaviour
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please provide as much detail as you can, it really helps us find and fix bugs faster.
+
+        #### Not a bug report?
+
+        * If you have a question \"How Do I ...?\", please post it on [GitHub Discussions](https://github.com/orgs/micropython/discussions/) or [Discord](https://discord.gg/RB8HZSAExQ) instead of here.
+        * For missing or incorrect documentation, or feature requests, then please [choose a different issue type](https://github.com/micropython/micropython/issues/new/choose).
+
+        #### Existing issue?
+
+        * Please search for [existing issues](https://github.com/micropython/micropython/issues) matching this bug before reporting.
+  - type: input
+    id: port-board-hw
+    attributes:
+      label: Port, board and/or hardware
+      description: |
+        Which MicroPython port(s) and board(s) are you using?
+      placeholder: |
+        esp32 port, ESP32-Fantastic board.
+    validations:
+      required: true
+  - type: textarea
+    id: version
+    attributes:
+      label: MicroPython version
+      description: |
+        To find the version:
+
+        1. Open a serial REPL.
+        2. Type Ctrl-B to see the startup message.
+        3. Copy-paste that output here.
+
+        If the issue is about building MicroPython, please provide output of `git describe --dirty` and as much information as possible about the build environment.
+
+        If the version or configuration is modified from the official MicroPython releases or the master branch, please tell us the details of this as well.
+      placeholder: |
+        MicroPython v6.28.3 on 2029-01-23; PyBoard 9 with STM32F9
+    validations:
+      required: true
+  - type: textarea
+    id: steps-reproduce
+    attributes:
+      label: Reproduction
+      description: |
+        What steps will reproduce the problem? Please include all details that could be relevant about the environment, configuration, etc.
+
+        If there is Python code to reproduce this issue then please either:
+        a. Type it into a code block below ([code block guide](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)), or
+        b. Post longer code to a [GitHub gist](https://gist.github.com/), or
+        c. Create a sample project on GitHub.
+
+        For build issues, please provide the exact build commands that you ran.
+      placeholder: |
+        1. Copy paste the code provided below into a new file
+        2. Use `mpremote run` to execute it on the board.
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected behaviour
+      description: |
+         What did you expect MicroPython to do? If comparing output with CPython or a different MicroPython port/version then please provide that output here.
+      placeholder: |
+        Expected to print "Hello World".
+
+        Here is the correct output, seen with previous MicroPython version v3.14.159:
+
+        > [...]
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: Observed behaviour
+      description: |
+        What actually happened? Where possible please paste exact output, or the complete build log, etc. Very long output can be linked in a [GitHub gist](https://gist.github.com/).
+      placeholder: |
+        This unexpected exception appears:
+
+        > [...]
+    validations:
+      required: true
+  - type: textarea
+    id: additional
+    attributes:
+      label: Additional Information
+      description: |
+        Is there anything else that might help to resolve this issue?
+      value: No, I've provided everything above.
+  - type: dropdown
+    id: code-of-conduct
+    attributes:
+      label: Code of Conduct
+      description: |
+        Do you agree to follow the MicroPython [Code of Conduct](https://github.com/micropython/micropython/blob/master/CODEOFCONDUCT.md) to ensure a safe and respectful space for everyone?
+      options:
+        - "Yes, I agree"
+      multiple: true
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to help improve MicroPython.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: MicroPython GitHub Discussions
+    url: https://github.com/orgs/micropython/discussions
+    about: Community discussion about all things MicroPython. This is the best place to start if you have questions about using MicroPython or getting started with MicroPython development.
+  - name: MicroPython Documentation
+    url: https://docs.micropython.org/
+    about: Documentation for using and working with MicroPython and libraries.
+  - name: MicroPython Downloads
+    url: https://micropython.org/download/
+    about: Pre-built firmware and information for most supported boards.

.github/ISSUE_TEMPLATE/documentation.yml

@@ -0,0 +1,46 @@
+name: Documentation issue
+description: Report areas of the documentation or examples that need improvement
+title: "docs: "
+labels: ["documentation"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        This form is for reporting issues with the documentation or examples provided with MicroPython.
+
+        If you have a general question \"How Do I ...?\", please post it on [GitHub Discussions](https://github.com/orgs/micropython/discussions/) or [Discord](https://discord.gg/RB8HZSAExQ) instead of here.
+
+        #### Existing issue?
+
+        * Please search for [existing issues](https://github.com/micropython/micropython/issues) before reporting a new one.
+  - type: input
+    id: page
+    attributes:
+      label: Documentation URL
+      description: |
+        Does this issue relate to a particular page in the [online documentation](https://docs.micropython.org/en/latest/)? If yes, please paste the URL of the page:
+      placeholder: |
+        https://docs.micropython.org/en/latest/
+  - type: textarea
+    id: version
+    attributes:
+      label: Description
+      description: |
+        Please describe what was missing from the documentation and/or what was incorrect/incomplete.
+    validations:
+      required: true
+  - type: dropdown
+    id: code-of-conduct
+    attributes:
+      label: Code of Conduct
+      description: |
+        Do you agree to follow the MicroPython [Code of Conduct](https://github.com/micropython/micropython/blob/master/CODEOFCONDUCT.md) to ensure a safe and respectful space for everyone?
+      options:
+        - "Yes, I agree"
+      multiple: true
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to help improve MicroPython.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,74 @@
+name: Feature request
+description: Request a feature or improvement
+labels: ['enhancement']
+body:
+  - type: markdown
+    attributes:
+      value: |
+        This form is for requesting features or improvements in MicroPython.
+
+        #### Get feedback first
+
+        Before submitting a new feature idea here, suggest starting a discussion on [Discord](https://discord.gg/RB8HZSAExQ) or [GitHub Discussions](https://github.com/orgs/micropython/discussions/) to get early feedback from the community and maintainers.
+
+        #### Not a MicroPython core feature?
+
+        * If you have a question \"How Do I ...?\", please post it on GitHub Discussions or Discord instead of here.
+        * Could this feature be implemented as a pure Python library? If so, please open the request on the [micropython-lib repository](https://github.com/micropython/micropython-lib/issues) instead.
+
+        #### Existing issue?
+
+        * Please search for [existing issues](https://github.com/micropython/micropython/issues) before opening a new one.
+  - type: textarea
+    id: feature
+    attributes:
+      label: Description
+      description: |
+        Describe the feature you'd like to see added to MicroPython. What does this feature enable and why is it useful?
+
+        * For core Python features, where possible please include a link to the relevant PEP or CPython documentation.
+        * For new architectures / ports / boards, please provide links to relevant documentation, specifications, and toolchains. Any information about the popularity and unique features about this hardware would also be useful.
+        * For features for existing ports (e.g. new peripherals or microcontroller features), please describe which port(s) it applies to, and whether this is could be an extension to the machine API or a port-specific module?
+        * For drivers (e.g. for external hardware), please link to datasheets and/or existing drivers from other sources.
+
+        If there is an existing discussion somewhere about this feature, please add a link to it as well.
+    validations:
+      required: true
+  - type: textarea
+    id: size
+    attributes:
+      label: Code Size
+      description: |
+         MicroPython aims to strike a balance between functionality and code size. Can this feature be optionally enabled?
+
+         If you believe the usefulness of this feature would outweigh the additional code size, please explain. (It's OK to say you're unsure here, we're happy to discuss this with you.)
+  - type: dropdown
+    id: implementation
+    attributes:
+      label: Implementation
+      description: |
+        What is your suggestion for implementing this feature?
+
+        (See also: [How to sponsor](https://github.com/sponsors/micropython#sponsors), [How to submit a Pull Request](https://github.com/micropython/micropython/wiki/ContributorGuidelines).)
+      options:
+        - I hope the MicroPython maintainers or community will implement this feature
+        - I intend to implement this feature and would submit a Pull Request if desirable
+        - I would like to sponsor development of this feature
+      multiple: true
+    validations:
+      required: true
+  - type: dropdown
+    id: code-of-conduct
+    attributes:
+      label: Code of Conduct
+      description: |
+        Do you agree to follow the MicroPython [Code of Conduct](https://github.com/micropython/micropython/blob/master/CODEOFCONDUCT.md) to ensure a safe and respectful space for everyone?
+      options:
+        - "Yes, I agree"
+      multiple: true
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to suggest improvements for MicroPython.

.github/ISSUE_TEMPLATE/security.yml

@@ -0,0 +1,60 @@
+name: Security report
+description: Report a security issue or vulnerability in MicroPython
+labels: ["security"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        This form is for reporting security issues in MicroPython that are not readily exploitable.
+
+        1. For issues that are readily exploitable or have high impact, please email contact@micropython.org instead.
+        1. If this is a question about security, please ask it in [Discussions](https://github.com/orgs/micropython/discussions/) or [Discord](https://discord.gg/RB8HZSAExQ) instead.
+
+        #### Existing issue?
+
+        * Please search for [existing issues](https://github.com/micropython/micropython/issues) before reporting a new one.
+
+  - type: input
+    id: port-board-hw
+    attributes:
+      label: Port, board and/or hardware
+      description: |
+        Which MicroPython port(s) and board(s) are you using?
+      placeholder: |
+        esp32 port, ESP32-Duper board.
+  - type: textarea
+    id: version
+    attributes:
+      label: MicroPython version
+      description: |
+        To find the version:
+
+        1. Open a serial REPL.
+        2. Type Ctrl-B to see the startup message.
+        3. Copy-paste that output here.
+
+        If the version or configuration is modified from the official MicroPython releases or the master branch, please tell us the details of this as well.
+      placeholder: |
+        MicroPython v6.28.3 on 2029-01-23; PyBoard 9 with STM32F9
+  - type: textarea
+    id: report
+    attributes:
+      label: Issue Report
+      description: |
+        Please provide a clear and concise description of the security issue.
+
+        * What does this issue allow an attacker to do?
+        * How does the attacker exploit this issue?
+    validations:
+      required: true
+  - type: dropdown
+    id: code-of-conduct
+    attributes:
+      label: Code of Conduct
+      description: |
+        Do you agree to follow the MicroPython [Code of Conduct](https://github.com/micropython/micropython/blob/master/CODEOFCONDUCT.md) to ensure a safe and respectful space for everyone?
+      options:
+        - "Yes, I agree"
+      multiple: true
+    validations:
+      required: true

.github/dependabot.yml

@@ -0,0 +1,7 @@
+version: 2
+updates:
+  # Maintain dependencies for GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "daily"