Enable website to display status reports
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- jekyll, markdown
- Domain
- build-system, ci-cd, documentation
Research direction
Start by reviewing the GitHub Pages/Jekyll setup and the rust-gcc/reporting repository, then compare the proposed workflow/CI release and nightly clone approaches. Check the pandoc org-to-gfm conversion, especially tables and C++ code blocks. Done means status reports are updated automatically and render correctly on the website.
Written by the indexing model from the issue text.
Description
- Switch to workflow/CI based releases instead of branch-based
- Figure out how to keep a submodule or equivalent to https://github.com/rust-gcc/reporting up to date
- Probably by cloning the repo every-night and redeploying the website?
- Figure out how to translate from org-mode to markdown or have github pages/jekyll display org-mode properly
---> This can be achieved by using thegfmexport format for pandoc:pandoc --from=org --to=gfm <file>.org > <file>.md
For the last point, note that pandoc screws up the tables as well as some formatting like C++ code-blocks. So we still have some modifications to do (or maybe we can convert org-mode directly to HTML?)
- Dominant language
- CSS
- Stars
- 10
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Rust-GCC/Rust-GCC.github.io
-
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
All issues in Rust-GCC/Rust-GCC.github.io
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
bigbio/sdrf-pipelines#372 · 1 comment ·
Maintainers usually reply within 1 day
-
yara-x fails to build with rsa 0.10.0: unresolved import rsa::Pkcs1v15SignPossibly taken @CfirTsabari claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 87/100
VirusTotal/yara-x#865 ·
Maintainers usually reply within 1 day
-
dependency-watch
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
beeblastco/broods#1433 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
Unable to buildOpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day