Repository navigation
Clarify website onboarding and fork staging previews - #908
LukasWallrich wants to merge 4 commits into
Conversation
|
👍 All image files/references (if any) are in webp format, in line with our policy. |
✅ Spell Check PassedNo spelling issues found when checking 1 changed file(s)! 🎉 |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="CONTRIBUTING.md">
<violation number="1" location="CONTRIBUTING.md:196">
P3: Monthly reports omit skipped PR numbers when every attempted PR conflicts because the workflow only emits that section when at least one PR was included. Fix the summary condition or qualify this documentation.</violation>
</file>
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
| - Successfully merged PRs | ||
| - Skipped PRs (with conflict details) | ||
| - Deployment statistics | ||
| - Skipped PR numbers (labelled as merge conflicts) |
There was a problem hiding this comment.
P3: Monthly reports omit skipped PR numbers when every attempted PR conflicts because the workflow only emits that section when at least one PR was included. Fix the summary condition or qualify this documentation.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At CONTRIBUTING.md, line 196:
<comment>Monthly reports omit skipped PR numbers when every attempted PR conflicts because the workflow only emits that section when at least one PR was included. Fix the summary condition or qualify this documentation.</comment>
<file context>
@@ -162,32 +175,26 @@ The FORRT website uses a dual deployment strategy to ensure quality and enable c
- Successfully merged PRs
-- Skipped PRs (with conflict details)
-- Deployment statistics
+- Skipped PR numbers (labelled as merge conflicts)
+- Aggregate branch and deployment time
</file context>
|
✅ Staging Deployment Status This PR has been successfully deployed to staging as part of an aggregated deployment. Deployed at: 2026-10-14 15:44:11 UTC The staging site shows the combined state of all compatible open PRs. |
There was a problem hiding this comment.
All reported issues were addressed across 1 file (changes from recent commits).
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
|
|
||
| - [Git](https://git-scm.com/downloads) | ||
| - [Hugo](https://gohugo.io/getting-started/installing/) | ||
| - [Hugo Extended](https://gohugo.io/getting-started/installing/) **0.158.0**, matching the production and staging workflows |
There was a problem hiding this comment.
the hugo version is optionnal , for development any latest version can work
|
|
||
| - [Git](https://git-scm.com/downloads) | ||
| - [Hugo](https://gohugo.io/getting-started/installing/) | ||
| - [Hugo Extended](https://gohugo.io/getting-started/installing/) **0.158.0**, matching the production and staging workflows |
There was a problem hiding this comment.
same here the version is optional
| ### How Staging Works | ||
|
|
||
| When a PR is opened, synchronised, or reopened, the staging workflow: | ||
| Automatic staging collects open, non-draft PRs targeting `main` and merges them in sequence onto a temporary branch. Conflicting PRs are skipped and logged. Inclusion in staging does not mean a PR has passed review or been approved for merging. The workflow posts staging results to PRs and retains two recent staging branches. |
There was a problem hiding this comment.
non-draft PRs are not auto deployed to staging
This branch has not been deployed
2 participants
Make the website contribution guide usable for first-time contributors: add browser-only content edits, correct fork/sync/push commands, pin Hugo Extended 0.158.0 to the workflows, and explain generated content and fork staging previews. Clarify the existing repository and contribution licences and link FORRT's Code of Conduct.
Validation: checked commands and staging behaviour against current deploy workflows; checked local link targets and the canonical conduct URL;
git diff --checkpassed. Opus 5.5 reviewed the guide, its findings were applied, and a final review approved it. Documentation only; no site build or deployment was run.Summary by cubic
Opens the website contribution guide to browser-only edits and aligns the fork workflow with how staging actually deploys.
data/publications.yamland the generatedstatic/data/fred_citation.txt.single_prpreview for external forks and the monthly report's skipped-PR list.Written for commit 5c36406. Summary will update on new commits.