Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add nightly generator for reports website #9

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

tanguysegarra
Copy link

@tanguysegarra tanguysegarra commented Dec 8, 2022

It looks like adding content to the reports section of the website can be quite repetitive and I believe gcc-rs maintainers' time is valuable and they should not be wasting some on that, so here's my attempt at implementing a generator to collect new reports every night and add them to the website.

@tanguysegarra tanguysegarra marked this pull request as ready for review January 18, 2023 12:56
Copy link
Member

@CohenArthur CohenArthur left a comment

Choose a reason for hiding this comment

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

As mentioned by @BastienGermond offline, this is good but it's missing a few things

  1. We don't import assets from the reporting repo (so things like images etc won't show properly)
  2. It's missing some jekyll information at the top of the markdown file which we should generate. Something like:
---
layout: post
title: "October 2022 monthly report"
author: Philip Herron and Arthur Cohen
tags:
    - monthly-report
---

I think this is a really good first start and we should start using it when these issues are fixed :)

[package]
name = "generator"
version = "0.1.0"
edition = "2021"
Copy link
Member

Choose a reason for hiding this comment

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

missing an author field here :D

Comment on lines +22 to +27
for report in reports_org_list {
match reports::convert(report, &cli.website) {
Ok(report_md) => {},
Err(e) => eprintln!("{:?}", e),
};
}
Copy link
Member

Choose a reason for hiding this comment

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

I think we should just display the monthly and yearly reports on the website. Otherwise, this would create too much noise. We can probably do a .filter() and filter on the name list. And since we have to generate markdown headers which contain yearly or monthly tag, we can do it twice with a different filter and act accordingly.

@@ -0,0 +1,29 @@
name: Nightly Build of Reports Website
Copy link
Member

Choose a reason for hiding this comment

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

Just thinking, but if we're adding a Rust project we should also add Rust checks to the CI. So something that builds generator on PRs and checks for clippy warnings.

i.e: https://github.com/Rust-GCC/bottleboard/blob/main/.github/workflows/check.yml or https://github.com/Rust-GCC/testing/blob/main/.github/workflows/build_check.yml

@CohenArthur CohenArthur self-assigned this Jan 18, 2023
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