Skip to content

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Sep 14, 2025

The project infrastructure is based on a collection of reusable assets, which are maintained in a centralized repository:

https://github.com/arduino/tooling-project-assets

Various minor improvements are hereby pulled into this project's infrastructure.

The `run` keys of the steps in the GitHub Actions workflows contain complex shell command lines.

The readability of this code is improved by selectively adding blank lines to separate it visually into logical
groupings.
Shell scripts in Arduino tooling projects are formatted according to the style implemented by the shfmt formatting tool.

In addition to standalone script files, significant quantities of complex shell code is also found in the asset tasks
and workflows. shfmt can not be used to format this code (both due to the fact it is in the form of strings in YAML
documents, and due to the fact that it is actually templates of shell code (making use of the templating features of
Task and GitHub Actions) rather than complete shell code). However, it still makes sense to align the formatting of this
code with the standardized shell code style where doing so is feasible.
The project's GitHub Actions workflows and tasks contain complex shell command lines.

With the use of the line continuation operator, these commands can be split into multiple code lines. This improves
readability by providing a visualization of the command structure and avoiding excessive line lengths. It also improves
maintainability by making diffs for changes to these commands more clear.

Previously this was done in many commands, but not consistently throughout the project.
The "Check Dependencies" templates store a cache of metadata about the licenses of dependencies under the `.licenses`
folder.

Since this folder only contains generated files, it should be excluded from the validation checks performed by unrelated
tools.

Previously, the markdownlint ignore configuration for this folder did not explicitly specify a location in the root of
the repository, meaning that it would result in ignoring a folder of that name at any location in the project. In cases
like this where a specific path is known, it is best to configure that exact path in order to avoid any chance of
unexpected behavior.
@per1234 per1234 self-assigned this Sep 14, 2025
@per1234 per1234 added type: enhancement Proposed improvement topic: infrastructure Related to project infrastructure labels Sep 14, 2025
Copy link

codecov bot commented Sep 14, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.33%. Comparing base (f6b2fd3) to head (7a90478).
⚠️ Report is 9 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #954   +/-   ##
=======================================
  Coverage   83.33%   83.33%           
=======================================
  Files           1        1           
  Lines         180      180           
=======================================
  Hits          150      150           
  Misses         19       19           
  Partials       11       11           
Flag Coverage Δ
unit 83.33% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@per1234 per1234 merged commit d1716cb into arduino:main Sep 14, 2025
71 of 74 checks passed
@per1234 per1234 deleted the sync branch September 14, 2025 06:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: infrastructure Related to project infrastructure type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant