Skip to content

Table freshness automation - #1309

Draft
kiemonbb wants to merge 4 commits into
masterfrom
table-freshness-automation
Draft

Table freshness automation#1309
kiemonbb wants to merge 4 commits into
masterfrom
table-freshness-automation

Conversation

@kiemonbb

Copy link
Copy Markdown

No description provided.

… table

Signed-off-by: Oktawian Bieszke <oktawian.bieszke@3mdeb.com>
Add new pre-commit check for outdated openness score table

Signed-off-by: Oktawian Bieszke <oktawian.bieszke@3mdeb.com>
@kiemonbb
kiemonbb requested a review from philipanda August 21, 2026 08:05
Comment thread scripts/check_fum_table_freshness.py Outdated
# Update this mapping when a device row is added/removed
# from the CSV, or when a platform's releases
# page is renamed or moved.
ROW_TO_RELEASE_PAGES = {

@macpijan macpijan Aug 21, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know it's an early PR but the early feedback is: I do not like it very much. If we move some manual updates from tables into script, the net benefit is not that great. What's mising to automatically build such a table based on the documentation content?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As for the table above, the script could match data from platforms overview.md pages to Firmware Update Method csv file, and generate such table on the run. Are there any other things, that caught your eye/could be done differently?

Comment thread scripts/check_fum_table_freshness.py Outdated
os.path.join(os.path.dirname(NOVACUSTOM_OVERVIEW), link)
).replace(os.sep, "/")

if "11th Gen" in label:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if we add new NovaCustom device? We have to add it again manually here?

Each device-specific function in this script essentially suggests that maybe we can do something else in the documentation to make it more consistent.

We should at least coinsider it. If not possible right now for some reason, we should create an issue for further discussion.

@kiemonbb kiemonbb Aug 21, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Each device-specific function in this script essentially suggests that maybe we can do something else in the documentation to make it more consistent.

We could add a new column to "docs/guides/firmware-update-method-support-table.csv" that wouldn't be rendered and would point to the actual release page of a platform. Then the whole scraping logic from this script would turn into just reading from the csv file.

@kiemonbb
kiemonbb force-pushed the table-freshness-automation branch from 277fb3b to 104313f Compare August 21, 2026 13:14
Signed-off-by: Oktawian Bieszke <oktawian.bieszke@3mdeb.com>
Signed-off-by: Oktawian Bieszke <oktawian.bieszke@3mdeb.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants